Vehicle access systems and methods

ABSTRACT

Systems, devices, and methods for controlling access to vehicles in rental, loaner, shared-use, and other vehicle fleets. Some of the present systems, devices, and methods use encrypted virtual keys that can be relayed to a vehicle computing device via a user&#39;s mobile device. Such virtual keys can be command-specific such that successful use of a virtual key results execution of a predetermined command or group of commands, and further commands require one or more additional virtual keys with the additional commands. Others of the present systems, devices, and methods provide tools: for provisioning or initial pairing of vehicle computing devices with corresponding vehicles, identifying and permitting a user to select locally available vehicles, prompting vehicle computing devices to retrieve pending commands from a server, and/or various other functions described in this disclosure.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/252,778 filed Nov. 9, 2015, the contents of which application areincorporated by reference in their entirety.

FIELD OF INVENTION

The present invention relates generally to vehicle rental and vehiclesharing and more particularly, but not by way of limitation, to systemsand methods for controlling access to shared or rented vehicles.

BACKGROUND

The prior art includes various systems and methods for multiple users toaccess and/or use a single vehicle, such as, for example, in car sharingservices and rental car services. Examples of car sharing servicesinclude Car2Go and ZipCar.

One example of a rental car service includes Silvercar. Historically,the Silvercar system has permitted a user of a smartphone running theSilvercar mobile application to scan a quick response (QR) code toidentify a vehicle to access, send a message to a server with the QRcode or data extracted from the QR code to identify the vehicle to theserver. If the selected vehicle was available for rental, the serverwould then send a command to a vehicle computing device—independent ofthe user's smartphone—to unlock the doors of the vehicle and change thevehicle to a “rented” state. Communications between the server and thevehicle also typically required an enterprise mobile application (on anadministrator device) to proxy the connection or relay messages betweenthe vehicle and the server.

SUMMARY

The present disclosure includes embodiments of systems and methods.

Some embodiments of the present systems comprise: a server comprising aportion of a reservation management (RM) system for a plurality ofvehicles, the server comprising memory and a processor configured toexecute instructions from the memory to: receive a request for access toa vehicle from a user's mobile computing device via an application onthe mobile computing device that is configured to interact with the RMsystem; generate two or more virtual keys for two or more of theplurality of vehicles, each virtual key being for a specific one of theplurality of vehicles and comprising an encrypted portion that includesa command for an action to be initiated by a vehicle computing device ofthe specific vehicle; an send the virtual keys to the requesting user'smobile computing device. Some embodiments further comprise: a vehiclecomputing device in communication with a controller area network (CAN)bus of a corresponding vehicle, the vehicle computing device comprisingmemory and a processor configured to execute instructions from thememory to: receive from the user's mobile computing device one of thevirtual keys; decrypt the encrypted portion of the virtual key; andinitiate the command for the corresponding vehicle.

Some embodiments of the present systems comprise: a mobile computingdevice; and a vehicle computing device in communication with acontroller area network (CAN) bus of a corresponding one of theplurality of vehicles. The mobile computing device can comprise aprocessor, memory, and an application stored in the memory andcomprising instructions configured to be executed by the processor to:receive, from a server of a reservation management (RM) system thatmanages usage of a plurality of vehicles, two or more virtual keys fortwo or more of the plurality of vehicles; receive a user's selection ofone of the plurality of vehicles to which one of the two or more virtualkeys corresponds; identify one of the virtual keys that corresponds tothe selected one of the plurality of vehicles; and transmit theidentified virtual key to the selected one of the plurality of vehicles.The vehicle computing device can comprise memory and a processorconfigured to execute instructions from the memory to: receive from themobile computing device the transmitted virtual key; decrypt theencrypted portion of the virtual key; and initiate the command for thecorresponding vehicle. In some embodiments, the application isconfigured to: permit a user to select one of the specific vehicles forwhich a virtual key is generated and sent to the user's mobile computingdevice; and delete any virtual keys for specific vehicles other than theselected one of the specific vehicles. In some embodiments, theapplication is configured to, after a virtual key has been successfullyreceived by a vehicle computing device of the corresponding vehicle andthe command executed, delete the executed virtual key from the mobilecomputing device. In some embodiments, the virtual keys include two ormore virtual keys for each of two or more of the plurality of vehicles.In some embodiments, the virtual keys include a first virtual keyincluding a command to begin a reservation with a first specificvehicle, and a second virtual key including a command to end areservation with the first specific vehicle. In some embodiments, thevirtual keys further include at least a third virtual key including acommand to unlock a door of the first specific vehicle, and a fourthvirtual key including a command to lock a door of the first specificvehicle.

Some embodiments of the present methods comprise: receiving a requestfor access to a vehicle; and generating two or more virtual keys for twoor more of the plurality of vehicles, each virtual key being for aspecific one of the plurality of vehicles and comprising an encryptedportion that includes: a command for an action to be initiated by avehicle computing device of the specific vehicle; and sending thevirtual keys to the requesting user's mobile computing device. In someembodiments, the request for access is received with a server of areservation management (RM) system for a plurality of vehicles; and sentfrom a user's mobile computing device via an application on the mobilecomputing device that is configured to interact with the RM system.

Some embodiments of the present systems comprise: a server comprising aportion of a reservation management (RM) system for a plurality ofvehicles, the server comprising memory and a processor configured toexecute instructions from the memory to: receive a request for access toa vehicle from a user's mobile computing device via an application onthe mobile computing device that is configured to interact with the RMsystem; generate two or more virtual keys for a specific one of theplurality of vehicles, each virtual key comprising an encrypted portionthat includes a command for an action to be initiated by a vehiclecomputing device of the specific vehicle; and send the virtual keys tothe requesting user's mobile computing device. Some embodiments furthercomprise: a vehicle computing device in communication with a controllerarea network (CAN) bus of a corresponding vehicle, the vehicle computingdevice comprising memory and a processor configured to executeinstructions from the memory to: receive from the user's mobilecomputing device one of the virtual keys; decrypt the encrypted portionof the virtual key; initiate the command for the corresponding vehicle;and

Some embodiments of the present systems comprise: a mobile computingdevice; and a vehicle computing device in communication with acontroller area network (CAN) bus of a corresponding one of theplurality of vehicles. The mobile computing device can comprise aprocessor, memory, and an application stored in the memory andcomprising instructions configured to be executed by the processor to:receive, from a server of a reservation management (RM) system thatmanages usage of a plurality of vehicles, two or more virtual keys for aspecific one of the plurality of vehicles, each virtual key comprisingan encrypted portion that includes a command for an action to beinitiated by a vehicle computing device of the specific vehicle; andreceive a user's selection of an action associated with or a commandincluded in one of the two or more virtual keys; identify one of thevirtual keys that corresponds to the selected action or command; andtransmit the identified virtual key to the selected one of the pluralityof vehicles. The vehicle computing device can comprise memory and aprocessor configured to execute instructions from the memory to: receivefrom the mobile computing device the transmitted virtual key; decryptthe encrypted portion of the virtual key; and initiate the command forthe corresponding vehicle. In some embodiments, a first one of thevirtual keys includes a command to begin a reservation with the specificvehicle, and a second one of the virtual keys includes a command to enda reservation with the specific vehicle. In some embodiments, a thirdone of the virtual keys includes a command to unlock a door of thespecific vehicle, and a fourth one of the virtual keys includes acommand to lock a door of the specific vehicle. In some embodiments, theapplication is configured to, after a virtual key has been successfullyreceived by a vehicle computing device of the corresponding vehicle andthe command executed, delete the executed virtual key from the mobilecomputing device.

Some embodiments of the present methods comprise: receiving a requestfor access to a vehicle; generating two or more virtual keys for aspecific one of the plurality of vehicles, each virtual key comprisingan encrypted portion that includes a command for an action to beinitiated by a vehicle computing device of the specific vehicle; andsending the virtual keys to the requesting user's mobile computingdevice. In some embodiments, the request is: received with a server of areservation management (RM) system for a plurality of vehicles; and sentfrom a user's mobile computing device via an application on the mobilecomputing device that is configured to interact with the RM system.

In some embodiments of the present systems, the processor of the serveris configured to, when generating a virtual key for a specific vehicle,execute instructions from the memory of the server to: access anencryption key that is unique to a specific vehicle; and utilize theaccessed encryption key to generate the encrypted portion of the virtualkey. In some embodiments, the decryption of the encrypted portion of avirtual key depends upon an encryption key known to the server and thevehicle device, but not known to the application on the user's portablecomputing device.

Some embodiments of the present system comprise: a server comprising aportion of a reservation management (RM) system for a plurality ofvehicles, the server comprising memory and a processor configured toexecute instructions from the memory to: receive a request for access toa vehicle from a user's mobile computing device via an application onthe mobile computing device that is configured to interact with the RMsystem; generate a virtual key for a specific one of the plurality ofvehicles, each virtual key comprising an encrypted portion that includea command for an action to be initiated by a vehicle computing device ofthe specific vehicle, where generating the virtual key for a specificvehicle includes accessing an encryption key that is unique to thespecific vehicle, and using the accessed unique encryption key togenerate the encrypted portion of the virtual key; and send the virtualkey to the requesting user's mobile computing device. Some embodimentsfurther comprise: a vehicle computing device in communication with acontroller area network (CAN) bus of a corresponding vehicle, thevehicle computing device comprising memory and a processor configured toexecute instructions from the memory to: receive from the user's mobilecomputing device one of the virtual keys; decrypt the encrypted portionof the virtual key; initiate the command for the corresponding vehicle;where the memory does not include unique encryption keys of others ofthe plurality of vehicles such that the vehicle computing device isunable to decrypt the encrypted portions of virtual keys for others ofthe plurality of vehicles. Some embodiments further comprise: a mobilecomputing device; and a vehicle computing device in communication with acontroller area network (CAN) bus of a corresponding vehicle. The mobilecomputing device can comprise a processor, memory, and an applicationstored in the memory and comprising instructions configured to beexecuted by the processor to: receive, from a server of a reservationmanagement (RM) system that manages usage of a plurality of vehicles, avirtual key for a specific one of the plurality of vehicles, the virtualkey comprising an encrypted portion that includes a command for anaction to be initiated by a vehicle computing device of the specificvehicle, where the encrypted portion is encrypted such that decryptionrequires an encryption key that is unique to the specific vehicle; andtransmit the virtual key to the selected one of the plurality ofvehicles. The vehicle computing device comprising memory and a processorconfigured to execute instructions from the memory to: receive from theuser's mobile computing device one of the virtual keys; decrypt theencrypted portion of the virtual key; and initiate the command for thecorresponding vehicle; where the memory does not include uniqueencryption keys of others of the plurality of vehicles such that thevehicle computing device is unable to decrypt the encrypted portions ofvirtual keys for others of the plurality of vehicles.

Some embodiments of the present methods: receiving a request for accessto a vehicle; generating a virtual key for a specific one of theplurality of vehicles, including accessing an encryption key that isunique to the specific vehicle and using the accessed unique encryptionkey to generate the encrypted portion of the virtual key, each virtualkey comprising an encrypted portion that includes a command for anaction to be initiated by a vehicle computing device of the specificvehicle; and sending the virtual key to the requesting user's mobilecomputing device. In some embodiments, the request for access isreceived with a server of a reservation management (RM) system for aplurality of vehicles; and sent from a user's mobile computing devicevia an application on the mobile computing device that is configured tointeract with the RM system.

In some embodiments of the present systems, the encrypted portion ofeach virtual key further includes: an identifier associated with thespecific vehicle. In some embodiments, the processor of the vehiclecomputing device is configured to execute instructions from the memoryof the vehicle computing device to: validate that the virtual keyidentifier associated with the specific vehicle matches an identifier ofthe corresponding vehicle.

In some embodiments of the present systems, the encrypted portion ofeach virtual key comprises the entire virtual key. In some embodiments,each virtual key further comprises an unencrypted portion.

In some embodiments of the present systems that comprise a vehiclecomputing device, the processor of the vehicle computing device isconfigured to execute instructions from the memory of the vehiclecomputing device to: in response to receiving a valid command to beginor end a reservation, change an availability status of the correspondingvehicle. In some embodiments, the processor of the vehicle computingdevice is configured to execute instructions form the memory of thevehicle computing device to: in response to a change in an availabilitystatus of the corresponding vehicle, send to the server a messageindicating the change in availability status. In some embodiments, themessage to the server indicating the change in availability statusincludes one or more characteristics of the vehicle obtained from theCAN bus.

In some embodiments of the present systems that comprise a vehiclecomputing device, the processor of the vehicle computing device isconfigured to execute instructions from the memory of the vehiclecomputing device to: in response to a change in ignition state of thevehicle, send to the server a message including one or morecharacteristics of the vehicle obtained from the CAN bus.

In some embodiments of the present systems that comprise a vehiclecomputing device, the processor of the vehicle computing device isconfigured to execute instructions from the memory of the vehiclecomputing device to: in response to the passage of a predeterminedperiod of time, send to the server a message including one or morecharacteristics of the vehicle obtained from the CAN bus.

In some embodiments of the present systems that comprise a vehiclecomputing device, the processor of the vehicle computing device isconfigured to execute instructions from the memory of the vehiclecomputing device to: in response to receiving an unencrypted messagefrom the server, send to the server a message including one or morecharacteristics of the vehicle obtained from the CAN bus.

In some embodiments of the present systems that comprise a vehiclecomputing device configured to send to the server a message includingone or more characteristics of the vehicle, the one or morecharacteristics of the vehicle include last odometer reading and fuellevel. In some embodiments, the message including the one or morecharacteristics is encrypted.

In some embodiments of the present systems that comprise a vehiclecomputing device, the vehicle computing device further comprises aglobal positioning system (GPS) module, and the message including one ormore characteristics of the vehicle obtained from the CAN also includesa location of the vehicle.

In some embodiments of the present systems that comprise a mobilecomputing device, the application is configured to, after a virtual keythat changes an availability status has been successfully received by avehicle computing device of the corresponding vehicle and the commandexecuted: send a message to the server indicating the change inavailability status. In some embodiments of the present systems thatcomprise a server, the server is configured to execute instructions fromthe memory of the server to: upon receipt of a message from one of thevehicle computing device or the user's mobile computing deviceindicating a change in availability state of a vehicle, determinewhether a corresponding message has also been received from the other ofthe vehicle computing device or the user's mobile computing device.

In some embodiments of the present systems, the encrypted portion of atleast one of the virtual keys further includes: an expiration timestampdefining the end of a time period by which the virtual key must be used;where the processor of the vehicle computing device is furtherconfigured to execute instructions from the memory of the vehiclecomputing device to, before executing the command of a virtual key withan expiration timestamp, validate that the expiration timestamp is notexpired. In some embodiments, each of the virtual keys includes anexpiration timestamp. In some embodiments, the processor of the vehiclecomputing device is further configured to execute instructions from thememory of the vehicle computing device to: execute an otherwise validcommand to end a reservation even if the timestamp of a virtual keyincluding the command is expired.

In some embodiments of the present systems, the encrypted portion of atleast one of the virtual keys further includes: a session identifier.

In some embodiments of the present systems that comprise a vehiclecomputing device, the processor of the vehicle computing device isfurther configured to execute instructions from the memory of thevehicle computing device to: in response to receiving a valid virtualkey with a command to begin a reservation, store the session identifier;and in response to subsequently receiving a virtual key with a commandto end the reservation, compare the session identifier of thesubsequently received virtual key to the stored session identifier; andif the compared session identifiers match, processing the command to endthe reservation.

In some embodiments of the present systems, at least one of the virtualkeys further comprises an unencrypted portion that includes: a keytimestamp; where the processor of the vehicle computing device isfurther configured to execute instructions from the memory of thevehicle computing device to: generate an initialization vector from atleast the key timestamp to decrypt the encrypted portion.

In some embodiments of the present systems, the decryption of theencrypted portion of a virtual key depends upon an encryption key knownto the server and the vehicle device, but not known to the applicationon the user's portable computing device.

In some embodiments of the present systems, where the encrypted portionof at least one of the virtual keys further includes: a validation code;where the processor of the vehicle computing device is furtherconfigured to execute instructions from the memory of the vehiclecomputing device to: generate a random challenge phrase; generate a hashstring from the validation code and challenge phrase; transmit thegenerated random challenge phrase to the user's mobile computing device;receive a hash string from the user's mobile computing device; andcompare the received hash string to the generated hash string tovalidate that the virtual key originated from an authorized user'smobile computing device. In some embodiments, the encrypted portion ofeach of the virtual keys further includes: a validation code. In someembodiments, the validation code comprises a reservation code specificto a reservation associated with the user.

In some embodiments of the present systems that comprise a vehiclecomputing device, the processor of the vehicle computing device isconfigured to execute instructions from the memory of the vehiclecomputing device to: if the corresponding vehicle is configured to becompatible with a smartkey and to determine whether the smartkey islocated in a cabin of the vehicle, query the CAN bus of thecorresponding vehicle to determine whether the smartkey is located inthe cabin. In some embodiments, the processor of the vehicle computingdevice is configured to not execute a command to end a reservationunless the smartkey is located in the cabin.

Some embodiments of the present systems comprise: a vehicle computingdevice configured to communicate with a controller area network (CAN)bus of a corresponding vehicle that is configured to be compatible witha smartkey and to determine whether the smartkey is located in a cabinof the vehicle, the vehicle computing device comprising memory and aprocessor configured to execute instructions from the memory to: receivea command for an action to be initiated by the vehicle computing deviceof the specific vehicle; decrypt the encrypted portion of the virtualkey; if the command is to end a reservation, query the CAN bus todetermine whether the smartkey is located in the cabin; and: if thesmartkey is located in the cabin, initiate the command; or if thesmartkey is not located in the cabin, send a signal to the user's mobilecomputing device to prompt the user to return the smartkey to the cabin.

Some embodiments of the present systems comprise: a vehicle computingdevice configured to communicate with a controller area network (CAN)bus of a corresponding vehicle that is configured to be compatible witha smartkey and to determine whether the smartkey is located in a cabinof the vehicle, the vehicle computing device comprising memory and aprocessor configured to execute instructions from the memory to:wirelessly receive a command to determine whether the smartkey islocated in the cabin; query the CAN bus to determine whether thesmartkey is located in the cabin; and wirelessly send a messageindicative of whether the smartkey is located in the cabin. Someembodiments further comprise: a server comprising a portion of areservation management (RM) system for a plurality of vehicles, theserver comprising memory and a processor configured to executeinstructions from the memory to: transmit commands to vehicle computingdevices each associated with one of the plurality of vehicles todetermine whether a smartkey associated with the vehicle is located inthe cabin; and receive signals from the plurality of vehicle computingdevices, each message indicative of whether the smartkey associated withthe corresponding one of the plurality of vehicles is located in thecabin of the vehicle.

In some embodiments of the present systems that comprise a vehiclecomputing device, the vehicle computing device does not communicate withthe CAN bus via an on-board diagnostic (OBD) port of the correspondingvehicle.

In some embodiments of the present systems that comprise a vehiclecomputing device, the vehicle computing device is not configured tocommunicate with the CAN bus via the OBD port.

Some embodiments of the present systems comprise: a mobile computingdevice comprising a processor, memory, a transceiver configured forlocal point-to-point communication, and an application stored in thememory and comprising instructions configured to be executed by theprocessor to: receive from a server of a reservation management (RM)system reservation information associated with a reservation for a userwith which the mobile computing device is associated; receive signalsfrom the local transceiver of each of one or more of a plurality ofvehicles that are within a communications range of the local transceiverof the mobile computing device, the received signals including anindication of the state record of the corresponding vehicle; validatethe reservation information; if the reservation information isvalidated, display to the user an indication of each of one or morevehicles that are available; receive from a user a selection of one ofthe available vehicle(s); and transmit the user's selection of one ofthe available vehicle(s) to the server. In some embodiments, theapplication further comprises instructions configured to be executed bythe processor to: receive from the server a plurality of virtual keysfor a plurality of available vehicles at a location corresponding tolocation of the reservation; where an indication of an available vehicleis not displayed if a virtual key has not been received from the serverfor that vehicle. In some embodiments, the application further comprisesinstructions configured to be executed by the processor to: receive fromthe server a virtual key for the selected one of the plurality ofvehicles; and transmit the virtual key to the selected one of theplurality of vehicles. In some embodiments, each virtual key is for aspecific one of the plurality of vehicles, and comprises an encryptedportion that includes: a command for an action to be initiated by avehicle computing device of the specific vehicle. Some embodimentsfurther comprise: a plurality of vehicles each comprising a vehiclecomputing device in communication with a controller area network (CAN)bus of the vehicle, the vehicle computing device comprising a processor,memory, and a local transceiver configured for local point-to-pointcommunications, the processor configured to execute instructions fromthe memory to: maintain a state record indicative of whether the vehicleis available to users; transmit via the local transceiver the state.Some embodiments further comprise: a server comprising a portion of areservation management (RM) system for a plurality of vehicles, theserver comprising memory and a processor configured to executeinstructions from the memory to: store a reservation for a user to useone of the plurality of vehicles; and transmit reservation informationassociated with the reservation to a mobile computing device associatedwith the user. In some embodiments, the processor of the server isconfigured to execute instructions from the memory to: receive from theuser's portable computing device a request for access including theuser's selection of the one of the available vehicles; generate avirtual key for the selected one of the available vehicles; and send thevirtual key to the user's mobile computing device. In some embodiments,the virtual key comprises an encrypted portion that includes: a commandfor an action to be initiated by a vehicle computing device of thespecific vehicle.

Some embodiments of the present systems comprise: a server comprising aportion of a reservation management (RM) system for a plurality ofvehicles, the server comprising memory and a processor configured toexecute instructions from the memory to: receive a message from amanufacturing work station configured to communicate with a vehiclecomputing device, the message including a unique identifier (UID)associated with the vehicle computing device; generate a uniqueencryption key from the UID; store the UID and the unique encryptionkey; generate a message that includes the unique encryption key for thevehicle computing device; and send the generated message to themanufacturing work station for storage in the vehicle computing device.In some embodiments, at least a portion of the generated message thatincludes the unique encryption key is encrypted. In some embodiments, atleast a portion of the received message is encrypted and the server isconfigured to execute instructions from the memory to decrypt thereceived message. Some embodiments, further comprising: the vehiclecomputing device configured to communicate with a controller areanetwork (CAN) bus of a vehicle, the vehicle computing device comprisingmemory and a processor, the memory storing a plurality of vehicle typesand settings associated with each vehicle type, the processor configuredto execute instructions from the memory to: query the CAN bus for theVIN of the vehicle; determine a vehicle type associated with the VIN;set the vehicle type in the nonvolatile memory of the vehicle computingdevice; and reboot with the settings associated with the set vehicletype. In some embodiments, the instructions to determine a vehicle typeassociated with the VIN include instructions to: generate a message thatincludes the VIN; send the message to the server; and receive a messagefrom the server with a vehicle type associated with the vehicle. In someembodiments, the message generated by the vehicle computing device alsoincludes the UID. In some embodiments, at least a portion of the messagereceived by the vehicle computing device is encrypted, and receiving themessage includes decrypting the received message. In some embodiments,at least a portion of the message generated by the vehicle computingdevice is encrypted. In some embodiments, generating the messageincludes encrypting at least a portion of the message. In someembodiments, at least a portion of the message received by the vehiclecomputing device is encrypted, and receiving the message includesdecrypting the received message.

Some embodiments of the present systems comprise: a vehicle computingdevice configured to communicate with a controller area network (CAN)bus of a corresponding vehicle, the vehicle computing device comprisingmemory and a processor, the memory storing a plurality of vehicle typesand settings associated with each vehicle type, the processor configuredto execute instructions from the memory to: query the CAN bus for avehicle identification number (VIN) of the vehicle; determine a vehicletype associated with the VIN; set the vehicle type in the nonvolatilememory of the vehicle computing device; and reboot with the settingsassociated with the set vehicle type. In some embodiments, theinstructions to determine a vehicle type associated with the VIN includeinstructions from to: generate a message that includes the VIN; send themessage to the server; receive a message from the server with a vehicletype associated with the vehicle. In some embodiments, the generatedmessage also includes the UID. In some embodiments, at least a portionof the received message is encrypted, and receiving the message includesdecrypting the received message. In some embodiments, at least a portionof the generated message is encrypted. In some embodiments, generatingthe message includes encrypting at least a portion of the message. Insome embodiments, at least a portion of the received message isencrypted, and receiving the message includes decrypting the receivedmessage.

Some embodiments of the present methods comprise: receiving a messageincluding a unique identifier (UID) associated with a vehicle computingdevice (the received message being: received with a server of areservation management (RM) system for a plurality of vehicles; and sentfrom a manufacturing work station configured to communicate with thevehicle computing device); generating a unique encryption key from theUID; storing the UID and the unique encryption key; generating a messagethat includes the unique encryption key for the vehicle computingdevice; and sending the generated message to the manufacturing workstation for storage in the vehicle computing device. In someembodiments, at least a portion of the generated message that includesthe unique encryption key is encrypted. In some embodiments, at least aportion of the received message is encrypted and the method furthercomprises: decrypting the received message. In some embodiments, atleast a portion of the generated message that includes the uniqueencryption key is encrypted. Some embodiments comprise: installing thevehicle computing device in a corresponding vehicle such that thevehicle computing device can communicate with a controller area network(CAN) bus of the corresponding vehicle. In some embodiments, the vehiclecomputing device comprises memory and a processor, the memory storing aplurality of vehicle types and settings associated with each vehicletype, and the method further comprises, after the vehicle computingdevice is installed in communication with a controller area network(CAN) bus of a corresponding vehicle: querying, with the processor ofthe mobile computing device, the CAN bus for a vehicle identificationnumber (VIN) of the vehicle; determining a vehicle type associated withthe VIN; setting the vehicle type in the nonvolatile memory of thevehicle computing device; and rebooting the mobile computing device withthe settings associated with the set vehicle type. In some embodiments,determining a vehicle type associated with the VIN comprises:generating, with the processor of the mobile computing device, a messagethat includes the VIN; sending the message to the server; receiving withthe mobile computing device a message from the server with a vehicletype associated with the vehicle. In some embodiments, the generatedmessage also includes a unique identifier (UID) associated with thevehicle computing device. In some embodiments, at least a portion of thereceived message is encrypted, and receiving the message includesdecrypting the received message. In some embodiments, at least a portionof the generated message is encrypted. In some embodiments, generatingthe message includes encrypting at least a portion of the message. Insome embodiments, at least a portion of the received message isencrypted, and receiving the message includes decrypting the receivedmessage.

Some embodiments of the present methods comprise: querying a controllerarea network (CAN) bus of a vehicle for a vehicle identification number(VIN) of the vehicle; determining a vehicle type associated with theVIN; setting the vehicle type in nonvolatile memory of a vehiclecomputing device in communication with the CAN bus, the vehiclecomputing device comprising memory storing a plurality of vehicle typesand settings associated with each vehicle type; and rebooting thevehicle computing device with the settings associated with the setvehicle type. In some embodiments, determining a vehicle type associatedwith the VIN comprises: generating a message that includes the VIN;sending the message to the server; and receiving with the mobilecomputing device a message from the server with a vehicle typeassociated with the vehicle. In some embodiments, the message alsoincludes a unique identifier (UID) associated with the vehicle computingdevice. In some embodiments, at least a portion of the received messageis encrypted, and receiving the message includes decrypting the receivedmessage. In some embodiments, at least a portion of the generatedmessage is encrypted. In some embodiments, generating the messageincludes encrypting at least a portion of the message. In someembodiments, at least a portion of the received message is encrypted,and receiving the message includes decrypting the received message.

Some embodiments of the present systems comprise: a vehicle computingdevice in communication with a controller area network (CAN) bus of acorresponding vehicle, the vehicle computing device comprising, acellular modem, memory, and a processor configured to executeinstructions from the memory to: receive a check-in prompt message froma server of a reservation management (RM) system; in response toreceiving the check-in prompt message, generate an encrypted check-inrequest message including a unique reference; send the encryptedcheck-in request message to the server; receive from the server anencrypted command message including one or more commands for the vehiclecomputing device; decrypt the command message; if the command message isconsistent with the unique reference in the encrypted check-in message,execute the one or more commands. Some embodiments further comprise: aserver comprising a portion of a reservation management (RM) system fora plurality of vehicles, the server comprising memory and a processorconfigured to execute instructions from the memory to: generate thecommand message including one or more command messages for the vehiclecomputing device; generate a check-in request message including a uniquereference; transmit the check-in message to the vehicle computingdevice; receive from the vehicle computing device an encrypted check-inmessage including a unique reference; decrypt the received check-inmessage; encrypt the command message using the unique reference; andsend the encrypted command message to the vehicle computing device. Insome embodiments, the check-in prompt message received by the vehiclecomputing device is not encrypted. In some embodiments, the vehiclecomputing device is configured to not execute command messages receivedvia the cell modem that are not sent by the server responsive to acheck-in request message sent to the server by the vehicle computingdevice. In some embodiments, the vehicle computing device is configuredto not execute command messages received from the server that are notsent by the server responsive to a check-in request message sent to theserver by the vehicle computing device.

Some embodiments of the present methods comprise: receiving a check-inprompt message with a vehicle computing device in communication with acontroller area network (CAN) bus of a corresponding vehicle, thecheck-in prompt message sent from a server of a reservation management(RM) system; generating, in response to receiving the check-in promptmessage, an encrypted check-in request message including a uniquereference; sending the encrypted check-in request message to the server;receiving from the server an encrypted command message including one ormore commands for the vehicle computing device; decrypting the commandmessage; and executing the one or more commands if the command messageis consistent with the unique reference in the encrypted check-inmessage.

Some embodiments of the present methods comprise: generating a commandmessage including one or more command messages for a vehicle computingdevice in communication with a controller area network (CAN) bus of avehicle; generating a check-in request message including a uniquereference; transmitting the check-in message to the vehicle computingdevice; receiving from the vehicle computing device an encryptedcheck-in message including a unique reference; decrypting the receivedcheck-in message; encrypting the command message using the uniquereference; and sending the encrypted command message to the vehiclecomputing device.

The term “coupled” is defined as connected, although not necessarilydirectly, and not necessarily mechanically; two items that are “coupled”may be unitary with each other. The terms “a” and “an” are defined asone or more unless this disclosure explicitly requires otherwise. Theterm “substantially” is defined as largely but not necessarily whollywhat is specified (and includes what is specified; e.g., substantially90 degrees includes 90 degrees and substantially parallel includesparallel), as understood by a person of ordinary skill in the art. Inany disclosed embodiment, the terms “substantially,” “approximately,”and “about” may be substituted with “within [a percentage] of” what isspecified, where the percentage includes 0.1, 1, 5, and 10 percent.

Further, a device or system that is configured in a certain way isconfigured in at least that way, but it can also be configured in otherways than those specifically described.

The terms “comprise” (and any form of comprise, such as “comprises” and“comprising”), “have” (and any form of have, such as “has” and“having”), “include” (and any form of include, such as “includes” and“including”), and “contain” (and any form of contain, such as “contains”and “containing”) are open-ended linking verbs. As a result, anapparatus that “comprises,” “has,” “includes,” or “contains” one or moreelements possesses those one or more elements, but is not limited topossessing only those elements. Likewise, a method that “comprises,”“has,” “includes,” or “contains” one or more steps possesses those oneor more steps, but is not limited to possessing only those one or moresteps.

Any embodiment of any of the apparatuses, systems, and methods canconsist of or consist essentially of—rather thancomprise/include/contain/have—any of the described steps, elements,and/or features. Thus, in any of the claims, the term “consisting of” or“consisting essentially of” can be substituted for any of the open-endedlinking verbs recited above, in order to change the scope of a givenclaim from what it would otherwise be using the open-ended linking verb.

The feature or features of one embodiment may be applied to otherembodiments, even though not described or illustrated, unless expresslyprohibited by this disclosure or the nature of the embodiments.

Some details associated with the embodiments described above and othersare described below.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings illustrate by way of example and not limitation.For the sake of brevity and clarity, every feature of a given structureis not always labeled in every figure in which that structure appears.Identical reference numbers do not necessarily indicate an identicalstructure. Rather, the same reference number may be used to indicate asimilar feature or a feature with similar functionality, as maynon-identical reference numbers.

FIG. 1 is a schematic block diagram illustrating one of the presentsystems.

FIG. 2 is a schematic block diagram illustrating a portion of the systemof FIG. 1.

FIG. 3 is a schematic block diagram illustrating a database suitable foruse in some of the present systems.

FIG. 4 is a schematic block diagram illustrating one embodiment of acomputer suitable for use with or in at least some of the presentsystems.

FIG. 5 depicts a schematic block diagram illustrating one embodiment ofserver suitable for use with or in some of the present systems.

FIG. 6 depicts a schematic block diagram illustrating one embodiment ofportable computing device suitable for use with or in some of thepresent systems.

FIG. 7 depicts an embodiment of one of the present vehicle computingdevices.

FIG. 8 depicts a schematic block diagram illustrating the functionalcomponents of one embodiment of firmware for the present vehiclecomputing devices, e.g., the one of FIG. 7.

FIG. 9 depicts a flowchart illustrating a process by which someembodiments of the present servers generate a virtual key.

FIG. 10 depicts a flowchart illustrating a process by which someembodiments of the present portable computing devices and/orapplications identify and display available vehicles for selection by auser.

FIG. 11 depicts a schematic block diagram conceptually illustrating auser interface for displaying available vehicles for selection by auser.

FIG. 12 depicts a flowchart illustrating a process by which someembodiments of the present portable computing devices and/orapplications obtain and transmit virtual keys to the present vehiclecomputing devices, and by which some embodiments of the present vehiclecomputing devices receive and process virtual keys.

FIG. 13 depicts a flowchart illustrating a process by which someembodiments of the present vehicle computing devices decrypt virtualkeys.

FIG. 14 depicts a flowchart illustrating a process by which someembodiments of the present vehicle computing devices and portablecomputing devices interact to verify that a virtual key sent to avehicle computing device originates with an authorized portablecomputing device.

FIG. 15 depicts a flowchart illustrating various availability states ofa vehicle and examples of typical transitions between the availabilitystates.

FIGS. 16A-16B depict flowcharts illustrating a process by which someembodiments of the present vehicle computing devices are paired with anew vehicle and information associated with the pairing is generated andstored in some embodiments of the present servers.

FIG. 17 depicts a flowchart illustrating a process by which at leastsome embodiments of the present servers and vehicle computing devicesinteract for the server to send command messages to the vehiclecomputing device.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Referring now to the drawings, and more particularly to FIG. 1, showntherein and designated by the reference numeral 100 is an embodiment ofthe present systems. In the embodiment shown, system 100 comprises aserver 104, and comprises and/or is configured to interact with one ormore interface devices 116. In some embodiments, interface devices 116can comprise one or more vehicle computing devices 112 a (e.g., coupledto at least one corresponding vehicle as described in more detail below)which can be configured to communicate with server 104 over a network116 (e.g., the Internet) via wireless communication path 120 such asCDMA, GSM, WiFi, and/or any other wireless communication path thatenables the functionality described in this disclosure. As conceptuallyillustrated, and as described in more detail below, some embodiments ofthe present vehicle computing devices 112 a can be configured tocommunicate with global positioning system (GPS) satellites 50 todetermine a position of the vehicle computing device 112 a. “GPS” isused generically herein to refer to any of various satellite positioningsystems, such as, for example, GPS, QZSS, GLONASS, Galileo,CompassBeidou, and/or the like. Many embodiments of the present systemswill comprise and/or be configured to interact with multiple vehiclecomputing devices 112 a. For example, many reservation management (RM)systems manage and/or coordinate usage of dozens, hundreds, or thousandsof vehicles, each of which would include its own vehicle computingdevice 112 a.

Interface devices 112 can additionally or alternatively comprise atleast one portable computing device 112 b (e.g., smart phones, tablets,and/or other portable computing devices, as will be described in moredetail below), which can be configured to communicate with server 104over a network 116 (e.g., the Internet) via wireless communication path120 such as, for example, CDMA, GSM, WiFi, and/or any other wirelesscommunication path that enables the functionality described in thisdisclosure. As conceptually illustrated, and as described in more detailbelow, a portable computing device 112 b can be configured tocommunicate directly with a vehicle computing device 112 a via a localpoint-to-point communication path 124 such as, for example, Bluetooth,Bluetooth Low Energy (BLE), and/or any other local point-to-pointcommunication path or protocol that enables the functionality describedin this disclosure. Many embodiments of the present systems willcomprise and/or be configured to interact with multiple vehiclecomputing devices 112 a.

Interface devices 112 can also include stationary and/or portablepersonal computers, such as, for example, to allow administrative and/orclient users to interact with server 104, vehicle computing devices 112a, and/or portable computing devices 112 b to perform various functions(e.g., add a vehicle to the system, create reservation, beginreservation, end reservation, unlock vehicle doors to permit vehicleaccess, and/or the like).

FIG. 2 conceptually illustrates one embodiment of a system 100 that canbe used to implement at least some of the present embodiments. System100 may include a server 104, a data storage device 128, a network 116,and an interface device 112. In some embodiments, server 104 may includestorage device 128 (e.g., a server housing or enclosure may housestorage device 128). In some embodiments, system 100 may include astorage controller 132, and/or a storage server configured to managedata communications between data storage device 128 and server 104and/or other components in communication with network 116. In someembodiments, storage controller 132 may be coupled to network 116 (e.g.,such that server 104 communicates or is configured to communicate withstorage controller 132 and/or storage device 128 via network 116. In ageneral embodiment, system 100 may be configured to store data (e.g.,vehicle records, user records, vehicle reservation and/or usage records,and/or the like). In some embodiments, system 100 is configured topermit multiple uses and/or functions to or with the data. For example,in some embodiments, system 100 is configured to permit multiple users(e.g., system administrative users, third-party administrative users,client users) to interact with the system simultaneously (e.g., a systemadministrative user adding a vehicle to the system, a third-partyadministrative user adding a reservation, a client user beginning areservation of a specific vehicle, and/or the like).

In some embodiments, server 104 is configured to access data stored indata storage device(s) 104 via a Storage Area Network (SAN) connection,a LAN, a data bus, or the like. Data storage device 128 may include ahard disk, including hard disks arranged in an Redundant Array ofIndependent Disks (RAID) array, a tape storage drive comprising amagnetic tape data storage device, an optical storage device, or thelike. In one embodiment, data storage device 128 stores various types ofdata, as described in more detail below. In some embodiments, server 104and/or storage device(s) 104 are configured to create a back-up (fulland/or partial back-up) of the data.

Interface device 112 is referred to broadly and comprises a suitableprocessor-based device such as, for example, a desktop computer, alaptop computer, a vehicle computing device 112 a, and/or a mobilecomputing device 112 b (e.g., a cellular phone, smartphone, etc.) havingaccess to the network 116. In some embodiments (e.g., mobile computingdevice 112 b), an interface device can be configured to access theInternet (e.g., via an application on the interface device or to accessa web application or web service hosted by server 104) and therebyprovide a user interface for enabling a user to enter or receiveinformation (e.g., from server 104). For example, a user may receive orview, via interface device 112, a webpage or an application screen(e.g., server 104 can transmit instructions to interface device 112 toinstruct or cause the interface device to render a webpage orapplication screen). By way of further example, in some embodiments(e.g., portable computing device 112 b), an interface device can beconfigured to receive input from a user (e.g., via user-input, such as atouchscreen and/or the like), can be configured to prompt (e.g.,visually) a user for input, and/or can be configured to transmit toserver 104 (e.g., via network 116) input received from a user.

In some embodiments, the functions described in this disclosure may beperformed by server 104 (e.g., interface device 112 may provide aterminal for accessing the computing/processing function of the server);may be performed by server 104 and an interface device 112 (e.g., server104 may perform some processing and interface device 112 may performsome processing); or may be performed entirely by interface device 112.For example, in some embodiments, a portable computing device 112 bincludes an application running on the device (e.g., a processorexecuting from memory instructions comprised by the application), suchthat all of certain functions are performed by the portable computingdevice. By way of further example, in some embodiments, a vehiclecomputing device 112 a includes firmware and/or software includingexecutable instructions in memory of the vehicle computing device thatcan be executed by a processor of the vehicle computing device.

FIG. 3 illustrates one embodiment of a data management system 200configured to store and manage data for the present embodiments. In oneembodiment, the system 200 may include a server 104. The server 104 maybe coupled to a data-bus as conceptually illustrated by the linesbetween the server and the storage devices. In one embodiment, thesystem 200 may also include a first data storage device 202, a seconddata storage device 204 and/or a third data storage device 206. Infurther embodiments, the system 200 may include additional data storagedevices (not shown). In such an embodiment, each data storage device202-206 may host a separate database of information. For example, insome embodiments, each of storage devices 202-206 can store or beconfigured to store different types of data (e.g., storage device 202storing vehicle records, storage device 204 storing user records,storage device 206 storing reservation and/or usage records, etc.). Insome embodiments, storage devices 202-206 may be arranged in a RAIDconfiguration for storing redundant copies of a database or databases(e.g., through synchronous or asynchronous redundancy updates).

In various embodiments, server 104 may communicate with data storagedevices 204-210 over a data-bus (illustrated by arrows between server104 and storage devices 202-206). In such embodiments, the data-bus maycomprise a SAN, a LAN, or the like. The communication infrastructure mayinclude Ethernet, Fibre-Channel Arbitrated Loop (FC-AL), Small ComputerSystem Interface (SCSI), and/or other similar data communication schemesassociated with data storage and communication. For example, server 104may communicate indirectly with data storage devices 202-206, (e.g., viaa storage server or storage controller 132).

Server 104 may host one or more software applications (e.g., web- and/orInternet-accessible software applications) configured and/or programmedto perform the functions described in this disclosure. The softwareapplication may further include modules configured to interface withdata storage devices 202-206, network 116, a user (e.g., via aninterface device 112), and/or the like. In a further embodiment, server104 may host an engine, application plug-in, or application programminginterface (API). In another embodiment, server 104 may host a webservice and/or other web accessible software application. In someembodiments, server 104 comprises one or more virtual servers.

FIG. 4 illustrates a computer system 300 adapted according to certainembodiments of server 104 and/or interface device 112. Centralprocessing unit (CPU) 302 is coupled to system bus 304. CPU 302 may be ageneral purpose CPU or microprocessor. The present embodiments are notrestricted by the architecture of CPU 302, as long as CPU 302 supportsthe modules, configurations, and/or operations as described herein. CPU302 may execute the various logical instructions according to thepresent embodiments. For example, CPU 302 may execute machine-levelinstructions according to the exemplary operations described below.Computer system 300 also may include Random Access Memory (RAM) 308,which may be SRAM, DRAM, SDRAM, or the like. Computer system 300 mayutilize RAM 308 to store the various data structures used by a softwareapplication configured as described in this disclosure. Computer system300 may also include Read Only Memory (ROM) 306 which may be PROM,EPROM, EEPROM, optical storage, or the like. ROM 306 may storeconfiguration information for booting computer system 300. RAM 308 andROM 306 may also store user and/or system 100 data.

Computer system 300 may also include an input/output (I/O) adapter 310,a communications adapter 314, a user interface adapter 316, and adisplay adapter 322. I/O adapter 310, communications adapter 314, and/orinterface adapter 316 may, in some embodiments, enable or a user tointeract with computer system 300 (e.g., to make, begin, or end areservation). In a further embodiment, display adapter 322 may display agraphical user interface associated with a software or web-basedapplication.

I/O adapter 310 may connect to one or more storage devices 312, such asone or more of a hard drive, a Compact Disk (CD) drive, a floppy diskdrive, a tape drive, to the computer system 300. Communications adapter314 may be adapted to couple computer system 300 to network 132, whichmay, for example, be one or more of a LAN, WAN, and/or the Internet.User interface adapter 316 couples user input devices, such as akeyboard 320, a pointing device 318, and a microphone and/or audiospeaker, to computer system 300. Display adapter 322 may be driven byCPU 302 to control the display on display device 324.

The present embodiments are not limited to the architecture of system300. Rather computer system 300 is provided as an example of one type ofcomputing device that may be adapted to perform the functions of aserver 104 and/or various interface devices 112. For example, anysuitable processor-based device may be utilized with appropriatespecial-purpose programming, including without limitation, includingcomputer game consoles, smart phones, tablets, and multi-processorservers. Other embodiments and configurations may omit certain elements.For example, as described in more detail below, vehicle computing device112 b does not include a user interface. Moreover, the presentembodiments may be implemented on application specific integratedcircuits (ASIC) or very large scale integrated (VLSI) circuits. In fact,persons of ordinary skill in the art may utilize any number of suitablestructures capable of executing logical operations according to thedescribed embodiments.

FIG. 5 illustrates a further embodiment of a server 104 for a vehiclemanagement (VM) system. In the embodiment shown, server 104 includes aplurality of modules configured to perform the functions described inthis disclosure. Although server 104 is described as having a pluralityof modules, in some embodiments, such modules are conceptual (e.g., suchmodules are not necessarily distinct physical pieces or segments ofcode, and may instead be combined into multiple combinations of themodules described, or into a single module that is configured to performsome or all of the functions described). In other embodiments, themodules described may be combined, omitted, and/or substituted in anycombination of individual modules and/or functions described. In theembodiments shown, server 104 broadly includes a vehicle module 350, auser module 354, a reservation module 358, and a communications module362.

In the embodiment shown, vehicle module 350 is generally configured toperform functions related to managing records associated with aplurality of vehicles the use of which is managed and/or coordinated bythe RM system. For example, vehicle module 350 may receive dataindicative of a vehicle the use of which is to be managed and/orcoordinated by the RM system, create a record associated with thatvehicle, and/or add and/or update information in that record as thevehicle is used. By way of further example, vehicle module 350 mayprovide information related to various vehicles (e.g., availablevehicles) to reservation module 358, such as, for example, in responseto a client action to initiate making a new reservation.

In the embodiment shown, user module 354 is generally configured toperform functions related to managing records associated with aplurality of users of the system, such as, for example, may be approvedor otherwise able to use vehicles managed by the system. For example,user module may receive information about a user, create a recordassociated with that user, and/or add and/or update information aboutthat user as the user interacts with the system. In some embodiments,security module 354 is configured to permit different levels of accessfor different users. Some users or types of users may be systemadministrators with administrator-level access to system 100, such as,for example, permission to read and edit files. Some users may havemore-limited access to system 100, such as, for example, third-partyadministrator users permission to read and edit only certain files, orclient users with permission to only read limited files, and/or thelike.

In the embodiment shown, reservation module 358 is generally configuredto interface with vehicle module 350 and user module 354 to respond toand/or fulfill user requests for reservations and/or other terms of useof vehicles managed by the VM system. For example, reservation module358 may receive a user request for a vehicle at a certain place and timeand communicate with vehicle module 350 to determine whether a vehicleis expected to be or could be made available at such place and time. Byway of further example, reservation module 358 may process requests tomodify, terminate, begin, or end a reservation.

In the embodiment shown, communication module 358 is generallyconfigured to coordinate communications and security protocols forcommunications (e.g., encryption) for various users interacting withserver 104 via network 116. For example, in some embodiments,communication modules 358 is configured to encrypt messages to differentsources in different ways, such as, for example, using different uniqueencryption keys for each of different vehicle computing devicesassociated with different vehicles, and/or using different encryptionprotocols with different types of user interface devices 112 (e.g., apersonal computer versus a smartphone, an Apple iOS phone versus anAndroid smartphone).

FIG. 6 illustrates a further embodiment of a portable computing device112 b. In the embodiment shown, device 112 b and, more particularly anapplication comprising instructions that are executable by a processorof device 112 b from memory of device 112 b, includes a plurality ofmodules configured to perform the functions described in thisdisclosure. Although device 112 b is described as having a plurality ofmodules, in some embodiments, such modules are merely conceptual (e.g.,such modules are not necessarily distinct physical pieces or segments ofcode, and may instead be combined into multiple combinations of themodules described, or into a single module that is configured to performsome or all of the functions described). In other embodiments, themodules described may be combined, omitted, and/or substituted in anycombination of individual modules and/or functions described. In theembodiments shown, device 112 b broadly includes a vehicle managementmodule 366, a vehicle command module 370, a security module 374, and autility module 378.

In the embodiment shown, vehicle management module 366 is generallyconfigured to perform functions related to identifying, filtering,and/or connecting/disconnecting local point-to-point communications withvehicles (e.g., vehicle computing modules 112 a) according to certaincharacteristics, such as, for example, availability status of a vehicle,proximity (e.g., communications signal strength), whether or not theapplication on portable computing device 112 b has a virtual key for thevehicle, and/or other characteristics. For example, and as described inmore detail below, vehicle management module 366 can be configured toscan for available vehicles in a user's location and display indicatorsof at least some of those vehicles to permit a user to select one of thevehicles to rent and/or otherwise use. By way of further example,vehicle management module may scan for and initiate communications witha particular vehicle in the user's location that is preselected for theuser to rent and/or otherwise begin a usage session.

In the embodiment shown, vehicle command module 370 (portable computingdevice 112 b) is generally configured to interact with the vehicle(e.g., vehicle computing device 112 a) to transmit commands (e.g., inthe form of virtual keys, as described in more detail below) for thevehicle. For example, and as described in the more detail below, vehiclecommand module 370 can be configured to transmit a virtual key to avehicle computing device 112 a of a corresponding vehicle to begin areservation with the corresponding vehicle, which virtual key mayinclude commands to unlock door(s), unlock and open the trunk, changethe availability state of the vehicle from “available” or “staged” to“rented” or “in use,” and or other commands. By way of further example,vehicle command module 370 can be configured to transmit virtual keyswith other commands, such as “lock” or “unlock,” during an activereservation. As another example, for administrator personal computingdevices 112 b (e.g., those with an administrator version of theapplication, or a version of the application with active administrativeprivileges), vehicle command module 370 may be configured to transmitcommands to change the availability state of a vehicle (e.g., afterbeing cleaned and refueled) from “returned” to “available” or “staged.”

In the embodiment shown, security module 374 is generally configured tomanage virtual keys and other application-specific security relatedfunctions, such as, for example, security protocols between portablecomputing device 112 b and vehicle computing devices 112 a, examples ofwhich are described in more detail below. For example, for some types ofvirtual keys (e.g., those including a command to start a reservation orend a reservation), once the virtual key has been transmitted from auser's phone (portable computing device 112 b) to a vehicle and thecommand(s) successfully executed by the vehicle, security module 374 canbe configured to delete the virtual key from the portable computingdevice so the user cannot use the same virtual key a second time. By wayof further example, and as described in more detail below, inembodiments in which virtual keys for multiple available cars aretransmitted to a user's phone (portable computing device 112 b), once auser has started a reservation for a particular one of the vehicles,security module 374 can be configured to delete virtual keys for anyother cars from the portable computing device so the user cannot start areservation with a second car (at least not without further interactionwith the system to ensure that the first reservation has ended andaccess to and use of the first car terminated).

In the embodiment shown, utility module 378 is generally configured toperform other, more-basic functions of the application on portablecomputing device 112 b. For example, in some embodiments, utility module378 can be configured to manage and present a user interface permittinga user to enter, and the application to receive and recognize userinputs of, requests for and creation of new reservations, selection of aparticular car from among a plurality of available cars,locking/unlocking or otherwise accessing a car, beginning and endingreservations with a particular available car, and/or the like. By way offurther example, the utility module 378 can be configured to performback-end functions that are ancillary to tasks primarily performed byother modules, such as, for example, requesting information (e.g., fuellevel, door lock state, window open state, whether a smartkey is presentin the cabin of the vehicle, and/or the like) from a vehicle computingdevice 112 a in conjunction with (e.g., which may be preconditions to)ending a reservation for that vehicle, and may be further configured totransmit that information to server 104 via network 116.

FIG. 7 depicts an embodiment of vehicle computing device 112 a. In thisembodiment, device 112 a comprises a printed circuit board with amicrocontroller 400 (including a processor and memory), a networkcommunications transceiver 404, a local point-to-point communicationstransceiver 408, a global positioning system (GPS) module 412, and/orone or more physical ports or connectors 416. In the embodiment shown,microcontroller 400 includes a processor and memory from which theprocessor can execute instructions. Any of various commerciallyavailable microcontrollers may be used, such as, for example, a “TIVA”series microcontroller made by Texas Instruments. In this embodiment,network communications transceiver comprises a cellular (e.g., CDMA orGSM) modem 420 and corresponding cellular antenna 424 and SIM cardholder 428. Any of various commercially available cellular modems may beused, such as, for example, cellular modules made by Telit WirelessSolutions. In some embodiments, device 112 a further comprises a WiFimodem. In the embodiment shown, local point-to-point communicationstransceiver 408 is comprised in a Bluetooth Low Energy (BLE) module thatincludes a transceiver, microcontroller, and an integrated antenna. Anyof various commercially available local point-to-point transceivers(e.g., as may be included in physically integrated communicationmodules) may be used, such as, for example, Bluetooth modules made byAnaren Inc. In the embodiment shown, GPS module 412 includes a receiverand microcontroller, and linked to a GPS antenna 432.

In the embodiment shown, ports 416 include at least a controller areanetwork (CAN) bus port configured to receive one end of a cable that isconfigured connect to a CAN bus connector of a corresponding vehicle. Inthis embodiment, vehicle computing device is configured to interact withthe CAN bus of a vehicle to which port 416 is connected to (i) sendcommands to the CAN bus to cause the vehicle to perform certain actions(e.g., lock/unlock doors, open trunk, chirp alarm, and/or the like),and/or (ii) retrieve characteristics of the vehicle (e.g., currentignition state, mileage or odometer reading, fuel level, and/or batteryvoltage). In some embodiments, the vehicle computing device (112 a) isalso configured to: in response to a triggering event, send to theserver a message (e.g., an encrypted message) including one or morecharacteristics of the vehicle obtained from the CAN bus. In at leastsome embodiments, triggering events can include the passage of apredetermined period of time (e.g., 25 hours), receipt of a message(e.g., an unencrypted message, as described in more detail below withreference to FIG. 17) from the server, the vehicle leaving a presetgeographic area, the vehicle traveling a distance in excess of a presetthreshold, and/or others (e.g., as described below).

In at least some embodiments, the vehicle computing device is notconfigured to (e.g., and does not) communicate with the CAN bus via anon-board diagnostic (OBD) port of the corresponding vehicle. Forexample, in some embodiments, the vehicle computing device (112 a) isconfigured to communicate with the CAN bus via a convenience moduleconnector of an AUDI vehicle, such as, for example, an AUDI model A3,S3, Q3, A4, S4, A5, S5, Q5, SQ5, A6, S6, A7, S7, RS7, SQ7, A8, S8, R8,TT, and/or TTS. At least some vehicles (e.g., AUDI vehicles) areconfigured to detect whether a contact-free smartkey (a smartkey thatneed not be physically seated in a socket or in contact with the vehicleto enable operation of the vehicle, which may be referred to in someinstances an “advanced key”) is located in a cabin of the vehicle and,for vehicles that are so configured, the vehicle computing device can beconfigured to query the CAN bus of the vehicle to determine whether thesmartkey located in the cabin (e.g., in response to receiving a commandfrom the server and/or an authorized smartphone) and/or transmit (e.g.,to the server and/or an authorized smartphone) an indication of whetherthe smartkey is located in the cabin. In systems configured with suchsmartkey-sensing functionality, the server can be configured to (i)transmit commands to one or more vehicle computing devices to determinewhether a smartkey associated with the corresponding vehicle is locatedin the cabin; and/or (ii) receive signals from the one or more vehiclecomputing devices each indicative of whether the smartkey associatedwith the corresponding vehicle is located in the cabin.

FIG. 8 depicts a schematic block diagram illustrating the functionalcomponents of one embodiment of firmware for the present vehiclecomputing devices, such as, for example, device 112 a as shown in FIG.7.

Embodiments of the present systems, such as system 100 of FIG. 1, can beconfigured to include any combination of the features described in thisdisclosure, such as is described in more detail below. In manyembodiments, server 104 comprises a portion of a reservation management(RM) system for a plurality of vehicles. For example, server 104 may beconfigured to interact with other servers, such as, for example,database servers configured to manage and serve read and/or writerequests for one or more databases of the RM system, and/or parallelfront-end servers that also (e.g., for load balancing and/or backup)interact with vehicle computing devices 112 a and/or user portablecomputing devices 112 b. As described above with reference to FIG. 3,servers (e.g., 104), vehicle computing devices (e.g., 112 a), andportable computing devices (e.g., 112 b) will each generally comprisememory (e.g., volatile and/or non-volatile) and a processor configuredto execute instructions from the memory, which—unless otherwiseindicated—is what is typically intended where this disclosure discussesa server, vehicle computing device, or portable computing device that isconfigured to perform a function. For example, that a server (e.g., 104)is configured to perform (or is described as performing) a functiontypically means that the server comprises memory and a processorconfigured to execute instructions from the memory to perform thefunction. Additionally, in the context of interactions betweencomponents (e.g., server 104 and a portable computing device 112 a), astatement that one component is configured to transmit or send an item(signal, message, virtual key, and/or the like) to another component;also indicates that the other component is configured to receive theitem, and vice versa. For example, a statement that the server isconfigured to receive from a user's portable computing device a requestfor access to a vehicle, also indicates that the user's portablecomputing device (e.g., application) is configured to send such arequest. Especially in the context of a portable computing device (e.g.,112 b), such instructions will typically be included in an applicationthat is stored in the memory, as is common for smartphones and tabletssuch as may run various mobile operating systems (e.g., iOS, Android,and/or the like).

In many of the present embodiments, server 104 is configured to receivea request for access to a vehicle from a user's mobile computing device(e.g., smartphone) 112 b via an application on the mobile computingdevice that is configured to interact with the RM system; and, inresponse (e.g., after validating the reservation) generate and send avirtual key to the user's smartphone, that the smartphone can thentransmit to a vehicle computing device 112 a to enable access to thecorresponding vehicle. For example, a user with a reservation canactivate an application on the user's smartphone 112 b request to beginthe reservation by gaining access to a vehicle, and the smartphone cantransmit the request to the server.

As illustrated in FIG. 9, server 104 can be configured to, responsive toreceiving (e.g., via cellular data network) a request for access to avehicle at a step 900 (and, in some embodiments, also responsive to orconditioned on validating certain aspects of a reservation and/or theuser's smartphone), generate and transmit a virtual key to the user'ssmartphone. In the depicted example, the vehicle computing devices (112a) each use a different encryption key for at least certain commands(e.g., at least some actions to be executed via the vehicles CAN bus)such that a command intended for a first vehicle and encrypted using afirst encryption key corresponding to the first vehicle (a vehiclecomputing device 112 a associated with the first vehicle) cannot bedecrypted or executed by a different vehicle (e.g., any of the othervehicles). As such, the illustrated process proceeds to a step 904 atwhich the encryption key corresponding to a particular vehicle isretrieved from memory (e.g., by vehicle module 350) to enable encryptionof a virtual key. In the illustrated example, server 104 and vehiclecomputing device 112 a are both configured to use Advanced EncryptionStandard (AES) encryption protocols as are known in the art. As such, aseed value is used to generate an initialization vector for use inencrypting the virtual key. In the example shown, a key timestamp suchas a generation timestamp (e.g., indicating the time at which therequest was received at step 900, or the time at which generation of thevirtual key or a first one of multiple virtual keys began) is created atstep 908 (e.g., by communications module 362). The generation timestampmay be created from a system clock, may correspond to a timestamp in themessage that included the request for access, and/or may be created invarious other ways.

In the illustrated example, the process then proceeds to a step 912 atwhich an initialization vector (IV) is generated (e.g., bycommunications module 362) from the encryption key retrieved in step 904and the generation timestamp created in step 908. In such embodimentsthe server (104) and the vehicle computing devices (112 a) of the systemeach has a common or shared algorithm used to generate the IV that isknown to both of the server and the vehicle computing device. Suchalgorithms are known in the art, with one example including: (i)generating a hash digest of the seed value, and (ii) select the requiredstring (e.g., 16 bytes) of data for the IV from the hash digest. Oncethe IV is generated, the process can proceed to step 916 at which datato be included in the virtual key is assembled and encrypted (e.g., bycommunications module 362), and may further be combined with unencrypteddata to generate the virtual key. While this example includes AESencryption using a timestamp for the seed value, other embodiments mayinclude different types of seed values and/or different types ofencryption protocols.

In at least some embodiments, after generation of the virtual key atstep 916, the virtual key corresponds to a specific vehicle, andincludes an encrypted portion (e.g., up to the entire virtual key) thatincludes a command for an action to be initiated by a vehicle computingdevice (112 a) of the specific vehicle. Examples of commands that may besuitable for and/or accessible to a customer user via the application onsmartphone 112 b users can include: start reservation, end reservation,unlock doors, and/or lock doors. Examples of commands that may besuitable for and/or accessible to an administrative user via anapplication on the administrative user's smartphone (e.g., via the sameapplication as the customer user, but in which additional functionalityis unlocked by the receipt of administrative credentials, or via adifferent administrative application) include: lock doors, unlock doors,change availability state, disable ignition, read fuel level, readbattery voltage or charge level, and/or the like. Some such commandsinclude multiple subparts. For example, a “start reservation” commandmay include subparts or subcommands for the vehicle computing device 112a to send messages to the CAN bus to cause the vehicle to unlock doorsand open the trunk; an “end reservation” command may include subparts orsubcommands for the vehicle computing device 112 a to send messages tothe CAN bus to cause the vehicle to determine whether a smartkey ispresent in the cabin of the vehicle and, if so, lock all doors of thevehicle. In addition to a command, the virtual key (e.g., the encryptedportion of the virtual key) can include additional pieces ofinformation, such as, for example, a validation code (e.g., areservation code that is unique to a particular reservation or usageperiod), a unique identifier (e.g., associated with a vehicle computingdevice for which the virtual key is intended), a session identifier(e.g. as described below), and/or the like, at least some of which aredescribed in more detail below.

In embodiments in which each of the vehicles includes a uniqueencryption key, the encryption key retrieved at step 904 is unique tothe specific vehicle (e.g., at least unique among the plurality ofvehicles for which use is managed by the RM system) such that if thevirtual key is inadvertently sent to an unintended vehicle, thatunintended vehicle cannot decrypt the (encrypted portion of) virtual keyor execute its command(s). In such embodiments, each vehicle computingdevice 112 a stores its assigned unique encryption key in memory of thevehicle computing device (e.g., and does not store unique encryptionkeys of other vehicle computing devices such that each vehicle computingdevice is not capable of decrypting virtual keys intended for othervehicles).

In the illustrated example, the process next proceeds to a step 920 inwhich the virtual key (e.g., having at least an encrypted portion) isthen transmitted (e.g., by communications module 362 of the server) tothe user's smartphone 112 b. In some embodiments, prior to betransmitted at step 920, a virtual key is bundled with other data, suchas, for example, the generation timestamp (whether as an encrypted orunencrypted part of the virtual key or a separate string of data) and/orone or more additional virtual keys). For example, in some embodiments,the server is configured to generate and transmit two or more virtualkeys (e.g., a “start reservation” virtual key, and an “end reservation”virtual key) for a single vehicle, or virtual keys for each of two ormore vehicles (e.g., “start reservation” virtual keys for each of two ormore vehicles, as described in more detail below.

FIG. 10 depicts a flowchart illustrating a process by which someembodiments of the present portable computing devices 112 b (e.g., viaan application on the portable computing device) identify and displayavailable vehicles for selection by a user. By way of example, rental orshared-use vehicle lots often include multiple vehicles that areavailable for rent or use, and the present systems can be configured topermit a user to select a particular one of the available vehicles. Inthe embodiment shown, the process begins at a step 1000 when a useractivates or provides input to an application (e.g., a graphical userinterface initiated by utility module 378) on the user's smartphone 112b to request access to a vehicle for a reservation.

In the example shown, the process then proceeds to a step 1104 at whichthe application (e.g., utility module 378) validates the reservation. Insome embodiments, validation is as simple as (1) determining whether theapplication has received confirmation of and/or other reservationinformation related to a reservation for (and/or within a predeterminedwindow of) the current date and time (e.g., via vehicle managementmodule 366), and/or (2) querying the server to determine whether theuser has a reservation for (and/or within a predetermined window of) thecurrent date and time (e.g., via utility module 378) and receivingresponsive reservation information (e.g., a message confirmingvalidation of the reservation and/or at least some details of areservation sufficient for the smartphone to directly validate thereservation). In other embodiments, validation may also includeverification of additional factors, such as, for example, current dateand/or time relative to reservation date and/or time, useridentification, credit card information and/or authorization, validityof user's driver's license, whether a pickup location of a reservationmatches the current (and/or within a predetermined range of) the user'scurrent location. If a reservation cannot be validated, the processterminates at 1008.

If a reservation is validated, the process can proceed to a step 1012 inwhich user's smartphone 112 b (e.g., vehicle management module 366)scans for local vehicles, such as, for example, via a localpoint-to-point communication protocol (e.g., Bluetooth or Bluetooth LowEnergy (BLE). For example, in some embodiments, vehicle computingdevices 112 a are configured to continuously or periodically broadcastan identification signal (e.g., at least when the car is available foruse or rental) such that, when scanning for vehicles, the user'ssmartphone can detect any vehicles that are broadcasting theidentification signal within communication range (as may be limited bycharacteristics of the transceivers of the smartphone and the vehiclecomputing device, and/or environmental conditions). In some embodiments,vehicle computing devices 112 a are also configured to maintain a staterecord indicative of whether the vehicle is available to users, andtransmit a current availability state with the identification signal,such that the identification signal received by user's smartphone 112 bincludes the availability state.

Once any vehicles within range have been identified, the process mayproceed to an optional step 1016 in which vehicles identified in step1012 are filtered for various characteristics (e.g., by vehiclemanagement module 366). For example, in embodiments in which the servertransmits one or more virtual keys to the user's smartphone 112 b priorto step 1000, filtering at step 1012 can include determining whether thesmartphone 112 b has a virtual key for each identified vehicle (e.g.,and discarding or noting in memory which vehicles the smartphone doesnot have virtual keys, so that such vehicles will not be displayed tothe user or will each be displayed in a way that indicates the lack of acorresponding virtual key).

In this example, the process can then proceed to a step 1020 in whichthe smartphone (e.g., vehicle management module 366) determines whetherany of the identified (e.g., as filtered) vehicles are available. Whilethis is shown as a separate step, in some embodiments step 1020 is anintegral part of step 1016 (e.g., availability is a characteristic usedto filter). In alternate embodiments, the vehicle computing devices (112a) are configured to broadcast the identification signal only when in anavailable state, or to broadcast the identification signal in adesignated way or mode only when in an available state, such that step1020 is inherently included in step 1012 because only available vehiclesare identified in step 1012. In this alternate embodiment, theinformation received by the smartphone inherently includes an indicationof the state record of the corresponding vehicle due to the fact that ithas been broadcast at all, or the fact that it has been broadcast in thedesignated way or mode. Once available vehicles are identified, theprocess can proceed to step 1024 in which, if one or more availablevehicles have been identified, the available vehicles are displayed to auser; or, if no available vehicles have been identified, the processterminates at 1008 to allow the user to reposition relative to thevehicles and begin again at step 1000.

FIG. 11 depicts a schematic block diagram conceptually illustrating auser interface 1100 for displaying available vehicles for selection by auser. As illustrated, the user's smartphone 112 b may receive via localpoint-to-point communications identification signals from the vehiclecomputing devices 112 a of each of multiple vehicles. When multiplevehicles are identified as available in steps 1012 and 1020, and are notfiltered out in step 1016, each of the vehicles (e.g., indiciaassociated with each vehicle) can be displayed to the user viasmartphone 112 b (e.g., by vehicle management module 366) for selection.In the illustrated example, the vehicles are displayed via a graphicuser interface 1100 that includes a carousel of images of license platesfor each of the vehicles. In other embodiments, license plate numbersare displayed rather than images, and/or the indicia are presented as astatic list rather than a carousel.

One the vehicles are displayed, the user can review the indicia (e.g.,license plates, as shown in the depicted example) that are displayed onthe smartphone, and input a selection 1104 (at step 1028 of FIG. 10) ofa selected vehicle 1108 the user wishes to use or rent (e.g., a car nearthe user's current location). When only a single vehicle is available,or in other embodiments in which a user is provided one or more virtualkeys for only a predetermined vehicle, the smartphone may display onlyindicia of that single vehicle without allowing the user to select fromamong multiple vehicles. Once a vehicle is selected, the smartphone isconfigured to proceed with either (1) sending to the server the requestfor access to the selected vehicle (which is received by the server atstep 900 of FIG. 9); or, (2) if the smartphone has already received a“begin reservation” key for the selected vehicle, sending the “beginreservation” virtual key to the vehicle computing device 112 a to theselected vehicle, such as, for example, the local point-to-pointcommunication protocol, as described in more detail with reference toFIG. 12.

FIG. 12 depicts a flowchart illustrating a process by which portablecomputing device 112 b (e.g., an application) can obtain and transmitvirtual keys to vehicle computing devices, and by which vehiclecomputing device 112 a can receive and process virtual keys. As shown,steps for each of the portable computing device (smartphone) and thevehicle computing device are shown. In the depicted example, the processbegins at a step 1200 in which a vehicle is or has been selected (e.g.,via vehicle management module 366). In configurations in which thesystem is configured to allow a user to select a particular vehicle(e.g., as described with reference to FIGS. 10 and 11), step 1200 maycorrespond to step 1028 (FIG. 10). In other configurations in which aspecific vehicle is preselected for a user, step 1200 may includereceiving information from the server identifying a particular vehicle.In either configuration, for embodiments in which one or more virtualkeys are initially sent to the user's smartphone (e.g., before a user'sselection of a specific vehicle, or before or simultaneously with servertransmitting an information identifying a pre-selected specific vehiclefor the user), the process includes an optional preliminary step 1204 inwhich the one or more virtual keys are received from the server. Step1204 may correspond, for example, to the receipt of one or more virtualkeys transmitted by the server at step 920 described with reference toFIG. 9.

In the depicted example, once a specific vehicle has been selected atstep 1200, the process proceeds to a step 1204 at which smartphone 112 a(e.g., via vehicle command module 370) determines a desired virtual key(e.g., a “start reservation” virtual key) has previously been receivedand is still stored on the smartphone. If not, the process can proceedto a step 1208 at which the smartphone transmits a request to the serverfor a virtual key. Where a reservation has not yet been started, step1208 can include, for example, sending (e.g., via vehicle managementmodule 366) information identifying the selected vehicle, such as isdescribed for step 1028 with reference to FIG. 10. Alternatively, whereinformation has previously been sent to or received from the server thatidentifies a selected vehicle, step 1208 can include, for example,sending (e.g., via command module 370) a request for a desired virtualkey (e.g., a “start reservation” virtual key) corresponding to theselected vehicle. At least partially in response to receiving therequest transmitted by the smartphone, the server can then generate andtransmit one or more virtual keys (e.g., as described with reference toFIG. 9) to the smartphone, and the process can then proceed to a step1216 at which the smartphone receives (e.g., via vehicle command module370) the virtual key(s) transmitted by the server.

In this example, once the one or more virtual keys are received, theprocess proceeds to a step 1220 in which the user's smartphone sends(e.g., via vehicle command module 370) the virtual key to the vehiclecomputing device (112 b) of the particular vehicle. Where multiplevirtual keys are received by the user's smartphone at step 1216, step1220 may, for example, including receiving user input selecting one ofthe virtual keys to be sent. For example, where “start reservation” and“end reservation” virtual keys are received, the smartphone can displayindicia (e.g., text and/or images) that a user can select, and receivesuch a selection such as via input to the user interface (e.g.,touchscreen) of the smartphone, to choose to send the “startreservation” virtual key. For illustration, the following describes theprocessing of one example of a “start reservation” virtual key, but isillustrative of at least some embodiments of the process for other typesof virtual keys as well (e.g., except with respect to functions orcommands to be performed by the vehicle computing device that areinherently specific to starting a reservation). In the example shown,the process then proceeds to a step 1224 at which the vehicle computingdevice (112 a) of the vehicle receives the “start reservation” virtualkey sent by the user's smartphone at step 1220. The process can thenproceed to a step 1228 at which the vehicle computing device decryptsthe received virtual key.

FIG. 13 depicts a flowchart illustrating a process by which vehiclecomputing device 112 a can decrypt virtual keys (e.g., at step 1228 ofFIG. 12). In the example shown, the decryption process begins at 1300and proceeds to a step 1304 at which the vehicle computing deviceretrieves the encryption key from memory (e.g., nonvolatile memory),such as, for example, the unique encryption key that is unique to thatvehicle, as described above. The process can then proceed to a step 1308at which the seed value (e.g., generation timestamp, as describedabove), is identified. For example, in embodiments in which the virtualkey includes an unencrypted portion with the seed value (e.g., thegeneration timestamp, as shown in FIG. 13 and described above), step1308 involves identifying that seed value. Steps 1304 and 1308 may occursimultaneously and/or step 1308 may occur before step 1304. Once thegeneration timestamp (or other seed value) is identified and theencryption key retrieved, the process proceeds to a step 1312 in whichthe vehicle computing device implement the common or shared algorithm(as described above with reference to FIG. 9) to generate theinitialization vector (IV) from the generation timestamp and theencryption key. Once the IV is generated, the process can proceed to astep 1316 in which the IV is used to decrypt the encrypted portion ofthe virtual key via the AES protocol, various implementations of whichare known. Once the encrypted portion of the virtual key is decrypted,the process ends at 1320.

Returning to FIG. 12, if decryption of the virtual key (e.g., theencrypted portion of the virtual key) is unsuccessful (e.g., because avirtual key was sent to an unintended vehicle), the process ends at1232. If instead the virtual key is successfully decrypted (e.g., viathe process described with reference to FIG. 13), the process proceedsto a step 1236 in which the vehicle computing device (112 a) initiatesan authorization process, and a step 1240 in which the user's smartphone(e.g., security module 374) engages in the initiation process, toconfirm that the virtual key originated from a smartphone of anauthorized user (e.g., and/or an authorized version of an application onthe user's smartphone).

FIG. 14 depicts a flowchart illustrating a process by which the vehiclecomputing device (112 b) and the smartphone (112 a) (e.g., securitymodule 374) interact to perform an authorization process (e.g., of steps1236 and 1240 FIG. 12) to verify that a virtual key sent to the vehiclecomputing device originates with an authorized smartphone. In theexample shown, the authorization process starts at 1400 and proceeds toan optional step 1404 at which the vehicle computing device determineswhether the information in the decrypted virtual key is valid (e.g.,includes all expected, or merely those required, data strings and/or thethat the data strings or of the expected or required length). If thedata cannot be validated, then the process terminates at 1408.

In some embodiments (such as the one shown), the authorization processrelies upon (and the encrypted virtual key includes) a reservationidentifier or code (e.g., including 6, 8, 10, 12, 14, or more digits).As such, if the data is validated at step 1408 (or if step 1408 isomitted), the process can proceed to a step 1416 at which the vehiclecomputing device parses the validation code (e.g., reservation) codefrom the decrypted data string(s) from the virtual key, after which theprocess can proceed to a step 1420 at which the vehicle computing devicegenerates a random challenge phrase (e.g., data string). Such achallenge phrase can be generated from any of various sources and in anyof various ways (e.g., selecting the first six digits of the time fromthe system clock) because the challenge phrase is used a seed orstarting value. Steps 1416 and 1420 may occur simultaneously and/or step1420 may occur before step 1416.

In the example shown, once the reservation code is parsed and achallenge phrase is generated, the process can proceed to a step 1424 atwhich a hash is generated from the challenge phrase and the reservationcode. The hash is generated from a common or shared hash function thatis known to both of the vehicle computing device and the smartphone. Anyof various known hash functions may be used, so long as the same hashfunction is used by both devices. The process can then proceed to a step1428 at which the vehicle computing device (112 a) sends the challengephrase to the smartphone (112 a) from which the virtual key originated,and a step 1432 at which the smartphone receives the challenge phrasefrom the vehicle computing device.

In this example, once the smartphone receives the challenge phrase atstep 1432, the process proceeds to a step 1436 at which the smartphoneuses the common or shared hash function to generate (e.g., via securitymodule 374) a hash from the challenge phrase and the reservation code.If the smartphone is authorized to have sent the virtual key to thevehicle computing device, then the smartphone will have also received,or will be authorized to retrieve, the reservation code from the server.For example, in at least some embodiments, the unique encryption keycorresponding to the vehicle computing device is not (e.g., and isnever) known to the smartphone, such that the smartphone is not capableof decrypting a virtual key that is received from the server andretransmitted to the vehicle computing device. In such embodiments, theserver may therefore transmit to the smartphone the reservation codeseparately from virtual key. Once the smartphone has is generated atstep 1436, the process can proceed to a step 1440 at which thesmartphone sends the smartphone-generated hash to the vehicle computingdevice, and a step 1444 at which the vehicle computing device receivesthe smartphone-generated hash.

In the example shown, once the smartphone-generated hash is received bythe vehicle computing device at step 1444, the process can proceed to astep 1448 at which the vehicle computing device compares thesmartphone-generated hash to the hash generated by the vehicle computingdevice at step 1424. If the two hashes do not match, the processterminates at 1412. If the two hashes match, the process endssuccessfully at 1452 with the authorization having been successful, andtherefore allowing the vehicle computing device to proceed withexecution of commands in the virtual key. In some embodiments, endingthe authorization process at 1452 includes storing a session identifierthat can be compared to a later command (e.g., an “end reservation”command) to verify that a subsequent “end reservation” virtual keyoriginates from the same user or smartphone that sent the “startreservation” command. In some embodiments, the reservation code is usedas the session identifier; but other embodiments may instead use adifferent value, such as, for example, a unique identifier of the user'ssmartphone that is initially sent to the server and included in theencrypted portion of the virtual key.

Returning again to FIG. 12, if authorization is not successful at step1236 and step 1240, the process on the vehicle computing device ends at1232, and on the smartphone ends at 1244. If instead, authorization atstep 1236 and step 1240 is successful, the process continues to a step1248 at which the vehicle computing device (112 a) determines whetherany applicable conditions are satisfied for execution of the command(s)included in the virtual key. By way of illustration, in someembodiments, the encrypted portion of the virtual key includes anexpiration timestamp defining the end of a time period by which thevirtual key must be used, after which the command(s) in the virtual keywill not be executed by the vehicle computing device. For example, for avehicle reservation beginning Monday at 12:00 pm and ending Tuesday at6:00 pm, the expiration timestamp in the “start reservation” virtual keymay be Monday at 11:00 pm, and/or the expiration timestamp in an “endreservation” virtual key may be Tuesday at 6:00 pm, such that the user'ssmartphone must make at least a supplemental contact with the server tobegin or end the reservation outside certain timed windows of thescheduled start and end times. In some embodiments, certain types ofcommands may be executed even if an expiration timestamp has expired;for example, an “end reservation” virtual key may, in someconfigurations, be executed even if the expiration timestamp has expired(e.g., as long as all other conditions for the “end reservation” virtualkey are met).

As a second example, in some embodiments, the encrypted portion of thevirtual key can include a unique identifier associated with an intendedvehicle computing device and that unique identifier may be compared atstep 1248 to the identifier of the vehicle computing device performingstep 1248 to ensure a match. For this second example, it may be notedthat in embodiments in which an encryption key unique to the vehiclecomputing device is required, successful decryption of a virtual key atstep 1128 inherently indicates that the virtual key has been received bythe vehicle computing device for which the virtual key was intended.However, even in such embodiments, the validation of a unique identifierassociated with the vehicle computing device may be included as asecondary validation.

In addition to the examples discussed above, in some embodiments,certain commands or types of commands may be associated with conditionsthat must be satisfied at step 1248 before the command and anysubcommands may be executed. For example, execution of a “startreservation” command may depend upon the vehicle having a currentavailability state of “available” or “staged” that indicates the vehiclehas been serviced as needed between rentals or usage periods, and hasnot been taken by a different user. By way of further example, executionof an “end reservation” command may depend upon the vehicle having acurrent availability state of “rented” or “in use,” a current ignitionstate of “off,” all doors being locked, and/or (in vehicles that areconfigured to detect whether a smartkey is located in the cabin) thatthe smartkey is located in the cabin.

In the illustrated example, if all applicable conditions are not met,the process ends at 1232. If instead all applicable conditions are metat step 1248, the process can proceed to a step 1252 at which thevehicle computing device executes the command(s) and any associatedsubcommands (which subcommands may be included in the virtual key or maybe stored in memory of the vehicle computing device for retrieval inconnection with the execution of types of commands with which thesubcommands are associated). For example, when executing a “startreservation” command, the vehicle computing device may perform all orsome of the following actions and/or other actions: (i) unlocking one ormore doors; (ii) opening the trunk; (iii) retrieving one or morecharacteristics of the vehicle (e.g., current ignition state, mileage orodometer reading, fuel level, vehicle location, and/or battery voltage),such as, for example, via the CAN bus, via the GPS module, or byretrieving from memory of the vehicle computing device values that werepreviously received from the CAN bus and/or the GPS module; and/or (iv)changing the availability of the vehicle state from “available” to“rented” or “in use.” By way of further example, when executing an “endreservation” command, the vehicle computing device may perform all orsome of the following actions and/or other actions: (i) retrieving oneor more characteristics of the vehicle (e.g., current ignition state,mileage or odometer reading, fuel level, vehicle location, and/orbattery voltage), such as, for example, via the CAN bus by retrievingfrom memory of the vehicle computing device values that were previouslyreceived from the CAN bus; and/or (ii) changing the availability of thevehicle state from to “rented” or “in use” to “returned” (e.g.,indicating that the vehicle is ready to be serviced before beingreturned to an “available” state) or, in some instances, from “rented”or “in use” to “available.”

In some embodiments, such as the one shown, step 1252 includes sendingfrom the vehicle computing device to the smartphone a confirmationmessage indicating that the command(s) and any associated subcommandshave been successfully executed. For example, successful execution ofcommand(s) and any associated subcommands for a “start reservation”virtual key may include sending to the smartphone (e.g., via the localpoint-to-point communication transceiver of the vehicle computingdevice) a confirmation message indicating that the vehicle state hasbeen changed to “rented” or “in use,” and/or may include some or all ofany retrieved characteristics of the vehicle. By way of further example,successful execution of commands and any associated subcommands for an“end reservation” virtual key may include sending (e.g., via the localpoint-to-point communication transceiver of the vehicle computingdevice) a confirmation message indicating that the vehicle state hasbeen changed to “returned” or “available,” and/or may include some orall of any retrieved characteristics of the vehicle. In suchembodiments, the process can proceed to a step 1256 at which thesmartphone receives the confirmation message sent by the vehiclecomputing device. In other embodiments, the confirmation message mayinstead be received from the server (e.g., after a report is sent fromthe vehicle computing device to the server, as described below).

Once the command(s) have been executed at step 1252, the process mayproceed to an optional step 1260 at which vehicle computing devicereports the execution of the command(s) to the server (e.g., via thecellular modem of the vehicle computing device), which report mayinclude a message similar to the confirmation message that may be sentfrom the vehicle computing device to the smartphone. Additionally oralternatively, the process may proceed to a step 1264 in which thesmartphone (e.g., utility module 378) reports the execution of thecommand(s) to the server (e.g., via the cellular modem of the vehiclecomputing device), which report may include a message similar to theconfirmation message that may be sent from the vehicle computing deviceto the smartphone. In embodiments in which the process includes both ofstep 1260 and step 1264, the server may be configured to (e.g., forsecurity and/or error-checking purposes) compare the informationincluded in the reports received from the smartphone and the vehiclecomputing device, and/or may signal a user (e.g., an administrative userof the system) of an error condition and/or possible security breach ifonly one of the two reports is received.

In some embodiments, the process can also proceed to an optional step1268 in which the smartphone (e.g., security module 374) deletes fromthe smartphone's memory a “start reservation” or an “end reservation”virtual key that has been successfully executed. By way of furtherexample, in embodiments in which multiple virtual keys are transmittedto a user's smartphone prior to beginning a reservation, at step 1268the smartphone (e.g., security module 374) may also delete unusedvirtual keys and/or virtual keys for vehicles other than the selected bythe user (e.g., for which a “start reservation” virtual key has beensent and successfully executed).

While the above example of a process for transmitting a virtual key fromthe smartphone (112 b) to the vehicle computing device (112 a) isprimarily described with reference to “start reservation” and “endreservation” virtual keys, in at least some of the present embodiments,the process—at least beginning with step 1208—is similar for any ofvarious types of virtual keys (e.g., start reservation, end reservation,lock, unlock, and/or the like).

FIG. 15 depicts a flowchart illustrating various availability states ofa vehicle and examples of typical transitions between the availabilitystates. In the example shown, a vehicle computing device 112 a may havean initial availability state of “new,” as indicated at 1500, prior tobeing associated with a particular vehicle. Once initiated in thesystem, and/or after being de-registered or unassociated with aparticular vehicle, the availability state may be changed to“unregistered,” as indicated at 1504. The availability state may befurther changed from “unregistered” to “hold,” as indicated at 1508,upon the vehicle being paired with a particular vehicle via a pairingprocess, such as, for example, the process described in more detailbelow with reference to FIGS. 16A-16B. From the “hold” availabilitystate, once the vehicle has reached a desired location and/or isotherwise ready to be used, the vehicle computing device may change to a“staged” or “available” state, as indicated at 1512, such as, forexample, in response to executing a “change state” virtual key, asdescribed above. From this “staged” or “available” state, the vehiclecomputing device may change to a “rented” available state as indicatedat 1516, such as, for example, in response to executing a “startreservation” or “change state” virtual key, as described above. From the“rented” or “in use” state, the vehicle computing device may change to a“returned” state as indicated at 1520, such as, for example, in responseto executing an “end reservation” or “change state” virtual key, asdescribed above. From the “returned” state, the vehicle computing devicemay return to the “staged” or “available” state indicated at 1512, suchas, for example, in response to executing a “change state” virtual key(including a command to change the state of the vehicle) received fromand sent by the server (104) or an administrative user's smartphone orother portable computing device 112 b (e.g., running the applicationwith administrative user authorization, or a distinct administrativeversion of the application).

Additionally, the vehicle computing device may change from the“returned” state to a “hold” state, as indicated at 1508, in response toexecuting a “change state” virtual key, as described above (e.g., whenthe vehicle needs maintenance or repairs in addition to more-typicalservices like cleaning or refueling). Further, the vehicle computingdevice may change from any of the other states to an “immobilized state”indicated at 1524, in response to executing a “change state” virtualkey, as described above (e.g., in response to the system or anadministrative user detecting fraud or theft related to the vehicle). Inan “immobilized” state, for example, the vehicle computing device maytrigger immobilization measures (e.g., interrupt power or other signalto prevent the vehicle from being started).

FIGS. 16A-16B depict flowcharts illustrating an example of a process bywhich a vehicle computing device (112 a) can be prepared for pairing andthen paired with a vehicle, and information associated with the pairinggenerated and stored in the server (104). More particularly, FIG. 16Ashows an example of the present processes by which a vehicle computingdevice is loaded with firmware and a unique encryption key, and FIG. 16Bshows and example of the present processes for pairing a vehiclecomputing device with a corresponding vehicle.

In the embodiment shown in FIG. 16A, the process begins at step 1600 andproceeds to a step 1604 at which a manufacturing work station (e.g., anaccess device 112 as described above with reference to FIG. 4)configured to communicate (e.g., in communication) with a vehiclecomputing device 112 b is used to load firmware into the memory of thevehicle computing device (V.C.D.). In some embodiments, the firmwareincludes a plurality of vehicle types (e.g., models) and settingsassociated with each model to enable the vehicle computing device tofunction with any of the vehicle types for which settings are stored.The process can then proceed to a step 1608 at which the manufacturingwork station requests from the vehicle computing device a uniqueidentifier (“unique ID” or “UID”) associated with the vehicle computingdevice. In response, at a step 1612, the vehicle computing reads the UIDfrom its memory and, at a step 1616, sends the UID back to themanufacturing work station. At a step 1620, the manufacturing workstation receives the UID from the vehicle computing device and, at astep 1624, sends the UID to server 104.

The process can then proceed to a step 1628 at which the server receivesthe UID and, at a step 1632, generates or otherwise assigns anencryption key for the vehicle computing device (e.g., a uniqueencryption key that is unique to that vehicle). For example, theencryption key may be or be generated from the UID or a portion of theUID, or a hashing function may be applied to the UID or a portion of theUID to generate an encryption key that is uniquely derived from the UIDor portion of the UID. Once the encryption key is generated, the processcan proceed to a step 1636 at which the UID (or portion of the UID) andthe encryption key associated with the particular vehicle computingdevice are stored. The process can then proceed to a step 1640 at whichthe server generates and sends a message (e.g., which may be encrypted)that includes the encryption key to the manufacturing work station forstorage in the vehicle computing device. The process can then proceed toa step 1644 at which the manufacturing work station receives theencryption key from the server, and a step 1648 at which themanufacturing work station sends the encryption key to the vehiclecomputing device. The vehicle computing device receives (and, ifnecessary, decrypts) the message with the unique encryption key andstores the encryption key in memory (e.g., nonvolatile memory) at step1652, and the illustrated example of a provisioning process ends at astep 1656.

In the embodiment shown in FIG. 16B, the pairing process starts 1660 andproceeds to a step 1662 at which the vehicle computing device isconnected to the vehicle CAN bus (e.g., a cable may be connected to bothof port 416 and a convenience port of the vehicle, as described above).The process can then proceed to a step 1664 in which the vehiclecomputing device (e.g., vehicle management module 370) queries the CANbus of the vehicle to determine a vehicle identification number (VIN)associated with the vehicle. The process can then proceed to a step 1666at which the vehicle computing device (e.g., vehicle management module370) sends a message (e.g., which may be encrypted) to the server withthe VIN or at least a portion (e.g., the last 10 of 17 characters) ofthe VIN and the unique ID associated with the vehicle computing device,and a step 1668 at which the server receives the message with the VIN.The process can then proceed to a step 1770 at which the server linksthe VIN and UID in a database, a step 1672 at which the server uses theVIN to look up a vehicle type (or model) with which the VIN isassociated, and a step 1674 at which the server sends a message with thevehicle type to the vehicle computing device. The process can thenproceed to a step 1676 at which the vehicle computing device receives(and decrypts, if necessary) the message with the vehicle type, and astep 1678 at which the vehicle computing device stores and/or otherwisesets the vehicle type in its memory (e.g., nonvolatile memory). Theprocess can then proceed to a step 1680 at which the vehicle computingdevice reboots itself and restarts with the settings associated with theset vehicle type. In other embodiments, the vehicle computing device mayinstead be configured to determine and set the appropriate vehicle typewithout requiring communication with the server (e.g., the vehiclecomputing device may still send the VIN and/or otherwise communicatewith the server, but may independently determine a vehicle type). Forexample, the vehicle computing device can include a lookup tableassociating certain VINs or portions of VINs with certain types ofvehicle types. Determine vehicle type without requiring servercommunication may, for example, be desirable in some instances in whicha limited number of (e.g., 10) vehicle types are associated with a knownrange of VINs (e.g., VINs in which only certain digits vary betweenvehicle types).

FIG. 17 depicts a flowchart illustrating an example of a process bywhich the server(s) (104) can interact with vehicle computing devices(112 a) to send command messages (e.g., virtual keys) to the vehiclecomputing device. In the embodiment shown, the process begins at step1700, such as, for example, in response to a triggering event indicatingthat a command should be sent to a vehicle. One example of a triggeringevent would be a report from a user that a rented vehicle has beenstolen, which would indicate that a “change state” command or virtualkey should be sent to the vehicle to change its availability state toincapacitated to prevent the vehicle from being restarted after itsengine is stopped. In this example, the process can proceed to a step1704 at which the server generates a vehicle command (e.g., in the formof an appropriate “change state” virtual key in the manner describedwith reference to FIG. 9). The process can then proceed to a step 1708at which the server (104) (e.g., communications module 362) sends acheck-in prompt message (e.g., an unencrypted check-in message) to thevehicle computing device, and a step 1712 at which the vehicle (e.g.,vehicle command module) receives the check-in message from the server.In some embodiments, the check-in prompt message is formatted as asimple SMS (short message service) message as is common for cellulartext messages. In some embodiments, the content of the check-in promptmessage are irrelevant to how the vehicle computing device responds tothe check-in prompt message; for example, the vehicle computing devicecan be configured to check-in with the server in response to receivingany SMS message.

Once the check-in prompt message is received, the process proceeds to astep 1720 in which the vehicle computing device generates an encryptedcheck-in request message (e.g., via a process similar to the onedescribed above with reference to FIG. 9). The process then proceeds toa step 1724 at which the vehicle computing device transmits theencrypted check-in request message to the server, and a step 1728 atwhich the server receives the encrypted check-in request message. Oncethe server receives the encrypted check-in request message from theserver at step 1728, the process can proceed to a step 1732 at which theserver decrypts the encrypted check-in request message (e.g., via aprocess similar to the one described above with reference to FIG. 13).

In some embodiments, the encrypted check-in request message generated bythe vehicle computing device (112 a) is formatted similar to at leastsome of the virtual keys described above (e.g., includes a command forthe server to transmit any queued commands, and a key timestamp or otherunique value, such as a generation timestamp, that the server can use toencrypt a command message or virtual key back to the vehicle). Once thecheck-in request message is decrypted at step 1732, the process canproceed to a step 1736 at which the server (104) encrypts a commandmessage (e.g., virtual key) including the vehicle command(s) previouslygenerated at step 1704. In some embodiments, the server uses the keytimestamp or other unique value encrypted in the check-in message to, inturn, encrypt the command message at step 1736. For example, the keytimestamp or other unique value can be used with the unique encryptionkey to generate an initialization vector (IV) to encrypt the commandmessage, and thereby further secure the command message or virtual keyagainst falsification by hackers or other unwanted intrusions (e.g.,without requiring a key timestamp to be sent as an unencrypted part ofthe command message). Once the command message is encrypted by theserver at step 1736, the process can proceed to a step 1740 at which theserver (e.g., communications module 362) sends the encrypted commandmessage to the vehicle computing device, and a step 1744 at which thevehicle computing device receives the command message.

Once the command message is received by the vehicle computing device,the process can proceed to a step 1748, at which the vehicle computingdevice begins a decryption and execution sequence similar to the onestarting at step 1228 of FIG. 12. For example, such a decryption andexecution sequence would generally proceed according to steps 1228-1248of FIG. 12, with the exception that step 1236 can be omitted. In thisembodiment, the vehicle computing device can be configured to comparethe received command message to the key timestamp or other unique valuethat was transmitted to the server in the check-in request message. Forexample, where the key timestamp is used with the unique encryption codeto generate the IV, encryption itself indicates that the command messagewas valid. In some embodiments, the key timestamp or other unique valueis also included in the encrypted portion of the command message andcompared after decryption (e.g., at step 1248) to further ensureconsistency. In embodiments of the present servers (104) and vehiclecomputing devices (112 a) configured to implement a process of the typeshown in FIG. 17, the vehicle computing device can be configured to notexecute command messages received via the cell modem and/or seeminglysent by the server that are not responsive to a check-in request messagesent to the server by the vehicle computing device (e.g., the vehiclecomputing device can be configured to take no action in response tounsolicited encrypted command messages).

The above specification and examples provide a complete description ofthe structure and use of illustrative embodiments. Although certainembodiments have been described above with a certain degree ofparticularity, or with reference to one or more individual embodiments,those skilled in the art could make numerous alterations to thedisclosed embodiments without departing from the scope of thisinvention. As such, the various illustrative embodiments of the methodsand systems are not intended to be limited to the particular formsdisclosed. Rather, they include all modifications and alternativesfalling within the scope of the claims, and embodiments other than theone shown may include some or all of the features of the depictedembodiment. For example, elements may be omitted or combined as aunitary structure, and/or connections may be substituted. Further, whereappropriate, aspects of any of the examples described above may becombined with aspects of any of the other examples described to formfurther examples having comparable or different properties and/orfunctions, and addressing the same or different problems. Similarly, itwill be understood that the benefits and advantages described above mayrelate to one embodiment or may relate to several embodiments.

The claims are not intended to include, and should not be interpreted toinclude, means-plus- or step-plus-function limitations, unless such alimitation is explicitly recited in a given claim using the phrase(s)“means for” or “step for,” respectively.

The invention claimed is:
 1. A system comprising: a server comprising aportion of a reservation management (RM) system for a plurality ofvehicles, the server comprising memory and a processor configured toexecute instructions from the memory to: receive a message from amanufacturing work station configured to communicate with a vehiclecomputing device, the message including a unique identifier (UID)associated with the vehicle computing device; generate a uniqueencryption key from the UID; store the UID and the unique encryptionkey; generate a message that includes the unique encryption key for thevehicle computing device; and send the generated message to themanufacturing work station for storage in the vehicle computing device.2. The system of claim 1, where at least a portion of the generatedmessage that includes the unique encryption key is encrypted.
 3. Thesystem of claim 1, where the received message is encrypted and theserver is configured to execute instructions from the memory to decryptthe received message.
 4. The system of claim 3, where at least a portionof the generated message that includes the unique encryption key isencrypted.
 5. The system of claim 1, further comprising: the vehiclecomputing device configured to communicate with a controller areanetwork (CAN) bus of a vehicle, the vehicle computing device comprisingmemory and a processor, the memory storing a plurality of vehicle typesand settings associated with each vehicle type, the processor configuredto execute instructions from the memory to: query the CAN bus for avehicle identification number (VIN) of the vehicle; determine a vehicletype associated with the VIN; set the vehicle type in a nonvolatilememory of the vehicle computing device; and reboot with the settingsassociated with the set vehicle type.
 6. The system of claim 5, wherethe instructions to determine a vehicle type associated with the VINcomprises instructions to: generate a message that includes the VIN;send the message to the server; and receive a message from the serverwith a vehicle type associated with the vehicle.
 7. The system of claim1, where the processor is further configured to execute instructionsfrom the memory to: generate a virtual key for a vehicle of theplurality of vehicles, the vehicle including the vehicle computingdevice, the virtual key comprising an encrypted portion that includes: acommand for an action to be initiated by the vehicle computing device;and where the instructions to generate the virtual key for the vehicleincludes instructions to: access the unique encryption key, and use theaccessed unique encryption key to generate the encrypted portion of thevirtual key.
 8. The system of claim 7, where the processor is furtherconfigured to execute instructions from the memory to: receive, from amobile computing device, a request for access to one of the plurality ofvehicles, the request associated with a rental reservation; and send thevirtual key to the mobile computing device; where decryption of theencrypted portion of the virtual key depends upon the unique encryptionkey that is known to the server and the vehicle computing device, butnot known to the mobile computing device.
 9. The system of claim 7,where the virtual key further comprises an unencrypted portion, wherethe unencrypted portion includes a unique reference, and where theunique reference is configured to enable decryption of the encryptedportion of the virtual key.
 10. A system comprising: a vehicle computingdevice configured to communicate with a controller area network (CAN)bus of a corresponding vehicle, the vehicle computing device comprisingmemory and a processor, the memory storing a plurality of vehicle typesand settings associated with each vehicle type, the processor configuredto execute instructions from the memory to: query the CAN bus for avehicle identification number (VIN) of the vehicle; determine a vehicletype associated with the VIN; set the vehicle type in a nonvolatilememory of the vehicle computing device; and reboot with the settingsassociated with the set vehicle type.
 11. The system of claim 10, wherethe instructions to determine a vehicle type associated with the VINincludes instructions to: generate a message that includes at least aportion of the VIN; send the message to a server; and receive a messagefrom the server with a vehicle type associated with the vehicle.
 12. Thesystem of claim 11, where at least a portion of the received message isencrypted, and receiving the message includes decrypting the receivedmessage.
 13. The system of claim 11, where at least a portion of thegenerated message is encrypted.
 14. The system of claim 13, where atleast a portion of the received message is encrypted, and receiving themessage includes decrypting the received message.
 15. The system ofclaim 14, where the generated message also includes a unique identifier(UID) associated with a vehicle computing device.
 16. The system ofclaim 10, where the memory is further configured to store a lookup tableassociating certain VINs or portions of VINs with certain types ofvehicle, and where the instructions to determine a vehicle typeassociated with the VIN include instructions to determine the vehicletype associated with the VIN based on the lookup table.
 17. The systemof claim 10, where the vehicle computing device is coupled to the CANbus via an on-board diagnostics (OBD) port or a convenience moduleconnector.
 18. A method comprising: receiving a message including aunique identifier (UID) associated with a vehicle computing device, themessage being: received with a server of a reservation management (RM)system for a plurality of vehicles; and sent from a manufacturing workstation configured to communicate with the vehicle computing device;generating a unique encryption key from the UID; storing the UID and theunique encryption key; generating a message that includes the uniqueencryption key for the vehicle computing device; and sending thegenerated message to the manufacturing work station for storage in thevehicle computing device.
 19. The method of claim 18, where at least aportion of the generated message that includes the unique encryption keyis encrypted.
 20. The method of claim 18, where at least a portion ofthe received message is encrypted and the method further comprises:decrypting the received message.
 21. The method of claim 20, where atleast a portion of the generated message that includes the uniqueencryption key is encrypted.
 22. The method of claim 18, furthercomprising: installing the vehicle computing device in a correspondingvehicle such that the vehicle computing device can communicate with acontroller area network (CAN) bus of the corresponding vehicle.
 23. Themethod of claim 18, where the vehicle computing device comprises memoryand a processor, the memory storing a plurality of vehicle types andsettings associated with each vehicle type, and the method furthercomprises, after the vehicle computing device is installed incommunication with a controller area network (CAN) bus of acorresponding vehicle: querying, with the processor of the mobilecomputing device, the CAN bus for a vehicle identification number (VIN)of the vehicle; determining a vehicle type associated with the VIN;setting the vehicle type in a nonvolatile memory of the vehiclecomputing device; and rebooting the mobile computing device with thesettings associated with the set vehicle type.
 24. The method of claim23, where determining a vehicle type associated with the VIN comprises:generating, with the processor of the mobile computing device, a messagethat includes the VIN; sending the message to the server; and receivingwith the mobile computing device a message from the server with avehicle type associated with the vehicle.
 25. A method comprising:querying a controller area network (CAN) bus of a vehicle for a vehicleidentification number (VIN) of the vehicle; determining a vehicle typeassociated with the VIN; setting the vehicle type in a nonvolatilememory of a vehicle computing device in communication with the CAN bus,the vehicle computing device comprising memory storing a plurality ofvehicle types and settings associated with each vehicle type; andrebooting the vehicle computing device with the settings associated withthe set vehicle type.
 26. The method of claim 25, where determining avehicle type associated with the VIN comprises: generating a messagethat includes at least a portion of the VIN; sending the message to aserver; and receiving with the mobile computing device a message fromthe server with a vehicle type associated with the vehicle.
 27. Themethod of claim 26, where generating the message includes encrypting atleast a portion of the message, and where the generated message alsoincludes a unique identifier (UID) associated with a vehicle computingdevice.
 28. The method of claim 27, where at least a portion of thereceived message is encrypted, and receiving the message includesdecrypting the received message.
 29. The method of claim 26, where thevehicle computing device is rebooted with the settings associated withthe set vehicle type responsive to setting the vehicle type in thenonvolatile memory.
 30. The method of claim 25, wherein the CAN bus ofthe vehicle is queried by the vehicle computing device responsive toconnecting the vehicle computing device to the CAN bus.